From: Ray K. <ra...@ga...> - 2009-03-04 16:10:17
|
On Mar 3, 2009, at 8:47 AM, John Huss wrote: > I believe this is implemented to use SQL in the FrontBase and > Postgres plugins. If MySQL supports it, then it probably wouldn't > be hard to add to the MySQL plugin. > > John > > On Tue, Mar 3, 2009 at 10:30 AM, Chuck Hill <chill@global- > village.net> wrote: > The last time I looked at this (and it was back in 5.0 IIRC), I saw > the same problem with FrontBase. > > ------------------------------------------------------------------------------ It has been true, since the port of WO to java, that this is how the JDBC has always implemented the fetchLimit. The benefit of using fetchLimit is that you get, probably, two copies of the data in the memory of your app (the snapshot in the database context and the eo in the editing context) and not three. In reality, there are often more copies of the eo than this floating around in different editing contexts. IMHO, the way to properly implement LIMIT has been to use SQL cursors, but nobody really proposes including the use of cursors in the SQL that is generated by EOF. Even I am not idealistic enough to propose it and I often like standards for their own sake. O well. There are certainly times it would be nice if EOF would use cursors, but there are probably many, many places one would have the fix EOF to make that work. cheers - ray |