Pierre van Rooden wrote:
Checked it out further, in server.xml of tomcat 4.1.27:
<ResourceParams name="jdbc/EmployeeAppDb">
-
<parameter>
<name>username</name>
<value>sa</value>
</parameter>
-
<parameter>
<name>password</name>
<value/>
</parameter>
-
<parameter>
<name>driverClassName</name>
<value>org.hsql.jdbcDriver</value>
</parameter>
-
<parameter>
<name>url</name>
<value>jdbc:HypersonicSQL:database</value>
</parameter>
</ResourceParams>IRRC: Older implementation had problem that someone did retrieve all the bytes from a string and tried to store the bytes. For HSQ this is a problem,.... for a string field it wants it data entered as an string and not as an byte array.I expect it will. All you need do is make a new configuration resource (similar to hsqldb) to test it. Configuration resources are in org.mmbase.storage.implementation.database.resources See:
I believe that this bug was introduced in old implementation classes to get mysql working with certain encodings.
This operation of casing strings to bytes is not needed for most databases(Only needed on mysql i think).
http://www.mmbase.org/download/builds/2003-08-22/mmdocs/backenddevelopers/storage/index.htmlGreat,.. i will have a look at it.
Is is true that we are making storage the default in 1.7? (otherwise lookup.xml is wrongly configured)
If this is the case, i'd like to see the whole module/database/implementation stuff moved to an alternative directory.
Furthermore we need a test plan, since i know that there are at lease 4 postgresql 7.X with jdbc 7.X drivers that need special attention.
-- Time is on my side,....
Eduard Witteveen +316 414 789 23
