Re: ORDA Limiting number of records returned.

2019-04-10 Thread Christian Sakowski via 4D_Tech
> YES! > I have done this for all BLOB or OBJECT heavy tables. > Just created a table called DOC_BLOBS > And only get the records in demand. > A world of difference ) Useless, because internally 4D stores BLOBs and Pictures not in the record by default. -- Grüße/Regards, [heubach-media] |

Re: ORDA Limiting number of records returned.

2019-04-10 Thread Eric Naujock via 4D_Tech
Well I guess I will be refactoring the tables. Originally the table was a monolithic table with hundreds of fields. I have been trying to pare it down by moving uncommon fields to other tables. > On Apr 10, 2019, at 10:13 AM, Herr Alexander Heintz via 4D_Tech > <4d_tech@lists.4d.com> wrote: >

Re: ORDA Limiting number of records returned.

2019-04-10 Thread Herr Alexander Heintz via 4D_Tech
Am 10.04.2019 um 16:09 schrieb Eric Naujock via 4D_Tech <4d_tech@lists.4d.com>: > > Related to the note about 4D Write Pro documents slowing things u. Would it > help to move all the 4D Write documents to a 4D Write table containing the > Write and Write Pro records? YES! I have done this for

Re: ORDA Limiting number of records returned.

2019-04-10 Thread Eric Naujock via 4D_Tech
Related to the note about 4D Write Pro documents slowing things u. Would it help to move all the 4D Write documents to a 4D Write table containing the Write and Write Pro records? The reason for this question is that if I start out with all the records I end up with a table that takes forever

Re: ORDA Limiting number of records returned.

2019-04-08 Thread Christian Sakowski via 4D_Tech
Currently the implementation returns not only a selection, it returns an unknown „page“ of records. So there comes maybe hundreds or more records during the first query. The second point is, that when there are object fields in the dataClass, the query may be very slow. We discovered a 10-13

Re: ORDA Limiting number of records returned.

2019-04-08 Thread Keisuke Miyako via 4D_Tech
ORDA queries only return a reference to the selection and not the entire data set, so it's not as if the payload should be a problem (especially at 35K which is small) but you could slice it to limit the size https://doc.4d.com/4Dv17R4/4D/17-R4/entitySelectionslice.305-4055325.en.html >

ORDA Limiting number of records returned.

2019-04-08 Thread Eric Naujock via 4D_Tech
Is there a way to limit the number of records returned in a ds..query result. I know about the set query limit in the system, but I am trying to do this new trick with order and want to be able to limit the results to only 1000 records max out of a table with over 35,000 rows. Any suggestions