> > I dont' think the databasesearch project / new database layers will be > > finished before 1.6 unless we delay its release even further, which I don't > > think is a good idea. If the databasesearch project can be far enough to > > make at least the 'limit' option possible reasonalby soon, then we could > > consider waiting for it, but I think it is perhaps better to leave the new > > query object away totally (at least the use of it), and finish it quitely > > for 1.7 in stead of rushing things now.
On behalf of the database search query project, some info: - We will indeed implement specifying limit and offset of results returned from a query, but as a database-specific feature. This functionality is not a standard feature in SQL92 databases, and where available syntax varies widely. - The project will take another couple of months to complete, so don't expect it to make it into the release 1.6. Regarding Eduards proposal: - I'm in favor to implement this just as a safeguard against overloading the server with useless large resultsets (like > 1000 results). Used this way, iit is not an alternative to the "limit" functionality discussed above. - It should not throw an exception, but just truncate the results and log a warning - isn't this what warnings are for? - Following the convention most common in Java, the value "no limit" should be represented by -1 instead of 0. Rob van Maris Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 -------------------------------------------------------------
