Re: paged query slow when fetching big lists

2007-06-26 Thread Marcin Skladaniec
Hi I have done some more profiling and testing. executing queries on table with 10 records, directly on server (not on client) gave results as listed below: 1) SelectQuery(Student.class) with page size 10 takes 30-50 seconds. 2) SQLTemplate(Student.class, SELECT #result('id' 'int') from

Re: paged query slow when fetching big lists

2007-06-26 Thread Andrus Adamchik
Hi Marcin, 1) SelectQuery(Student.class) with page size 10 takes 30-50 seconds. 2) SQLTemplate(Student.class, SELECT #result('id' 'int') from STUDENT) without paging takes 100 sec. 3) SQLTemplate(Student.class, SELECT #result('id' 'int') from STUDENT) with page size 10 takes 5 sec. 4)

Re: paged query slow when fetching big lists

2007-06-26 Thread Marcin Skladaniec
Hi Andrus ! Many thanks for that ! Marcin On 26/06/2007, at 5:39 PM, Andrus Adamchik wrote: Hi Marcin, 1) SelectQuery(Student.class) with page size 10 takes 30-50 seconds. 2) SQLTemplate(Student.class, SELECT #result('id' 'int') from STUDENT) without paging takes 100 sec. 3)

Exception: No property for arcId

2007-06-26 Thread Michael Lepine
Hello all. I am getting the CayenneRuntimeException below when trying to invoke the setToOneTarget on one of my generated classes. The _Req and _DepartmentPrefix classes are generated classes. This same code worked yesterday morning but after some updates to the database and subsequent updates to

Re: paged query slow when fetching big lists

2007-06-26 Thread Andrus Adamchik
Hi Marcin, I have good news (I think). Fetching just id columns inside the IncrementalFaultList indeed speeds things up significantly. I just committed the change to optimize SelectQueries to do just that. Please let me know how does it work for you. Now the profiling details... * I

Re: paged query slow when fetching big lists

2007-06-26 Thread Marcin Skladaniec
Hi Andrus ! The fix you committed today works great, I can confirm, in our case the 30-50 second SelectQuery now executes in 5-7 seconds ! There is one but: fix does work only for queries executed on server, when I executed the query on (ROP) client, the query takes the same amount of