We have seen this problem since migrating the mysql driver to the
com.mysql version. In our case, changes to the application logic took
care of the problem. Specifically, we would need to call
setDateCreated() on the user object.
The problem may actually be in torque rather than turbine since the
default (not specified in the schema) is set to '0000-00-00 00:00:00'
for both the CREATED and the LAST_LOGIN columns in TURBINE_USER.
cheers,
h.
On Jun 9, 2006, at 2:38 AM, Wohlschlaeger, Fabian wrote:
5h work and i found the error.
Turbine setted some timestamps in the turbine-user table 0000-00-00
00:00:00
and this couldn't be converted to a timestamp, so Torque, which is
used by
TurbineSecurity, throws an exception. I hope u are able to fix the
bug with
my explanation.
Nice Greetings
Fabian Wohlschlänger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
