<Kees Jongenburger:> > As far as I understand in MMBase you almoost always need 2 query get a > node (one to find out in what database table the node is stored and on > to actualy find the node). It thing this migth be a problem, is it > possible to define the table to query in the PreparedStatement after > the statement was created?
No, the tablename can not be parametrized in a PreparedStatement. However, I don't see why this should be a problem, apart from the fact that you'll need more PreparedStatement instances (consuming more resources). > There are 3 more things that might be of interest to you As a matter of fact, none of these are of interest, since the proposal only deals with how connection from the connectionpool handle prepared statements. It does not care how the statements are created.I insist on pointing this out, to avoid confusion about what the proposal is actually about. Also, Gerard's proposal is (already) part of the Query project, providing ways to tune query handing for better performance. The project will result in a (database)layer that handles Query objects transparently - you'll never have to worry about how the resulting queries are actually executed. Rob van Maris Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 -------------------------------------------------------------
