I have the exact same problem. After some debugging, I
found out that
the problem lies on the way village translates the output of the jdbc
driver. The drivers returns an integer for the fields of type
bit (1 for
true, 0 for false). Village obviously (I don't have the source code)
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
Hi,
in the current Torque API, there is no way to get the Connection pool. I
would guess this is an anti-feature.
If you are ready to patch Torque, you can change the relevant methods in
TorqueInstance to public. If not, only a hack comes to my mind: Configure
the pool in JNDI, use the
