I forgot to finish my thought. What Tom could do is query for ALL the data, excepting the image data, then have a custom script that loads the images for just the visible records. This would preserver the ability to use findRecord and findIndex on the full set of the already queried and stored data in the datagrid, while maintaining efficiency for the visible images.
Bob S > On Nov 8, 2019, at 12:58 , Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > If he only queries for the data for the visible records. Otherwise the query > is going to take as long as it takes to DL all the data. > > I was thinking some time ago about developing some paging scripts for the > datagrid, using the LIMIT function of SQL, but I never actually had a reason > for it. Also it dawned on me that I could not use findRecord or findIndex on > a limited range of the data contained in the dgData. > > I have a datagrid that loads file data as in saved fillable form PDFs stored > in large BLOB columns, and when I got to 15 forms or so, and I was on a slow > connection, working with the Forms module took a substantial time to load all > the data. > > What I did instead is just before making the query I deleted the column > containing the form data from the select clause, so I only queried for > columns not containing large amounts of form data. I query for the form data > only when needed. > > Bob S _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
