The same bug exists in both version 3.1.7 which I used for mysql4, and 3.1.12, the latest version.
Even if there was a special driver for mysql4, the same problem would exist, since the BIT type is new in mysql. If the latest driver does not understand it , why would the old one do??? Antonis Thomas Fischer wrote <[EMAIL PROTECTED]>: > > > > > Hm, not easy to work with buggy drivers... > > Just a crazy idea: Is it possible to use a mysql4 driver for a mysql5 > database ? > > Thomas > > [EMAIL PROTECTED] schrieb am 28.12.2005 20:45:08: > > > Thomas Fischer wrote <[EMAIL PROTECTED]>: > > > > > > > > > > > > > > > > > Hi, > > > > > > The property files were converted into java classes. They are located > in > > > the subpackage "platform" of the generator. > > > > > > From your mail, it seems that the behaviour of the mysql driver changed > > > from mysql4 to mysql5.If I remember correctly, the bit type worked > > > correctly for mysql4 (I used the test project to check this, there is a > > > test case for bit in there). I'll try to check the bit type against > mysql5 > > > in the next days. > > > > > > As a workaraound, you can use the booleanint or booleanchar types. > > > > > > Thomas > > > > > > > Hi, > > I looked into the problem and the problem lies on a bug of jdbc > connector > > (org.gjt.mm.mysql.Driver). It reports the type of BIT fields to be > > 12 instead of > > -7 (java.sql.Types). > > I checked the bug list of MySQL: the bug has already been reported and > a > > couple of solutions have been commited. The correction will be available > with > > the new release. Until then, I'm thinking of "patching" the source code > of > > Village (com.workingdogs.village.Column.populate(ResultSetMetaData rsmd, > int > > colNum, String tableName)), but I'm not sure that this is the only method > that > > uses the buggy code. > > > > Antonis > > > > -- > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
