On Mon, Jun 30, 2008 at 5:30 AM, Øyvind Harboe <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 30, 2008 at 11:01 AM, Andrus Adamchik
> <[EMAIL PROTECTED]> wrote:
>> There is no lazy fetching of attributes (only relationships). We will be
>> adding it at some point. It is a bit more involved than simply su
I discovered that for some of the cases it is the relationships that
actually cause the massive memory consumption, not the
unused columns.
Once I realized this, I modified my app to do the following:
- perform a normal query. Everything into memory using a normal query.
- do some simple checks o
On Jun 30, 2008, at 3:23 PM, Scott Anderson wrote:
If I'm not mistaken, using an incomplete SQLTemplate statement will
allow fetching of incomplete DataObjects, and Cayenne will not go
back to the database again until you try to access unfetched data.
In this case Cayenne will create compl
opped at a breakpoint where cayenne was persuaded to resolve DataObjects for
display in the debugger's trace window.
-Original Message-
From: Andrus Adamchik [mailto:[EMAIL PROTECTED]
Sent: Monday, June 30, 2008 5:01 AM
To: user@cayenne.apache.org
Subject: Re: Memory usage and select st
>
>
> Ah. I can see how the app uses more and more memory then.
>
> I assume the only way the relationship is broken is to gc the top level
> object.
Alternatively, you can use ValueHolder.invalidate() on top-level (reverse)
property. However, I'm not 100% sure that'll work.
BTW, I tried to map
On Mon, Jun 30, 2008 at 11:32 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
> No weak reference, but all relationships are faulted lazily.
Ah. I can see how the app uses more and more memory then.
I assume the only way the relationship is broken is to gc the top level
object.
BTW, I tried to ma
No weak reference, but all relationships are faulted lazily.
Andrus
On Jun 30, 2008, at 12:30 PM, Øyvind Harboe wrote:
On Mon, Jun 30, 2008 at 11:01 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
There is no lazy fetching of attributes (only relationships). We
will be
adding it at some poin
On Mon, Jun 30, 2008 at 11:01 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
> There is no lazy fetching of attributes (only relationships). We will be
> adding it at some point. It is a bit more involved than simply suppressing a
> given column in the SQL translator. Still you have a few of option
On Mon, Jun 30, 2008 at 11:01 AM, Andrus Adamchik
<[EMAIL PROTECTED]> wrote:
> There is no lazy fetching of attributes (only relationships). We will be
> adding it at some point. It is a bit more involved than simply suppressing a
> given column in the SQL translator. Still you have a few of option
There is no lazy fetching of attributes (only relationships). We will
be adding it at some point. It is a bit more involved than simply
suppressing a given column in the SQL translator. Still you have a few
of options:
1. Place large columns in a separate table with 1..1 relationship to
t
An SQL statement includes a list of which columns to fetch for
the query.
Consider a table "book" with three columns, id(pk), title(<100 chars)
and content(the entire text of the book).
SELECT id, title FROM book
If one of the columns are big and rarely used, then it makes little
sense to transf
11 matches
Mail list logo
