On Thu, 2002-09-26 at 15:55, Kees Jongenburger wrote: > I think I understand what the "hack" does. But I don't understand > the motivation(what problem does it solve?) The problem of multiple jdbc-drivers and mutliple databases. When we add this functionality, there is no need to document 'how-to-setup-database-layer' for the users, and a configuration can be selected upon the config of the user.
For example, when do you use the hsql and when the hsqldb? I also planned to create a new postgresql implementation(7.2 seems to have problems with byte-stuff), and i think it would only lead to a lot of errors, when there become more and more implementations. Furthermore, why would you like to configure your database-layer, if MMBase can detect it itselve? If you like to set it in the normal way, that is still possible, and i guess it will stay so. > why is a jndi datasrouce not supported at this ime? Since MMBase supports java 1.2, and naming is needed for jndi, which is java version 1.3. I posted a new jdbc module, which offers this functionality. > and why make thing fuzzy? How would you like to see it work? Any better idea's? > my gues would be to just write documentation about what is possible. > maybe move the database <property name="database">hsqldb</property> to > jdbc.xml > provide links to jdbc drivers? Moving the database property to jdbc.xml doesnt seem a good idea, since jdbc module provides us an jdbc-connection and has nothing to do with the MMBase database-implementation-settings. IRC: I proposed this also once and you talked me out of it ;) (look inside mmbaseroot.xml inside cvs) Furthermore, im not going to document all possible cross-combinations of all jdbc-driver database's for example: postgresql7.0 postgresql7.1 postgresql1.2 jdbc-driver from 7.1 works on 7.0 database jdbc-driver from 7.2 works on 7.1, only byte stuff has to be handled different and we also have the other jdbc driver for postgresl (for example jxDBCon). We already have here 9 possible combinations. With this you can detect if you support the combination, or not. -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
