On Thu, 2002-08-01 at 17:15, Gerard van de Looi wrote: > Further I think we need the following features in this layer: > - Prepared statements Do you mean Prepare statements like they are defined in JDBC or in some other way?
> - Multiple database support (optimized queries per database) The new query-interface _should_ provide a tree of conditions on which there has to be searched. I think this will make optimalisation also possible but it has to be kept in mind at this moment. > - Scrollable resultsets in case of large query results Quite difficult as this moment. This would mean that an search that does "SELECT * FROM OBJECT" should give a List back, and that it scrolls on itselve when you access an not yet resolved node. The problem here is that to use scrolling, you would like to keep you connection. Since most queries come from the cache it's quite hard (imho) to implement something like this > I think we can use something like the DAO pattern > (http://java.sun.com/blueprints/patterns/j2ee_patterns/data_access_object/in > dex.html) to implement this layer. Extensions for some kind of generic query > representation is needed to be able to dynamically cunstruct queries from > our applications. Could you give some additional information of you you would like to see DAO to be used? (i dont know that much about it) -- Eduard Witteveen Systeem Ontwikkelaar NOS Internet, Gateway C Kamer 107 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
