Sven Richter wrote:
Dear Stefano,
yes, the whole timestamp issue is also a problem for me (in my database
there are also no entries for Creation Date). But my problem was lying
before that. In my case there was no user created at all and I got an
error message. And I found out why. The autoincrement mechanism for the
user_id isn't working, so the database is using the default ('0'). And
in my database table there was already an user with the user_id '0'.
That's why I got this error message. But I don't know why autoincrement
isn't working. I have a couple of other tables, where it's working just
fine.
By the way, I use the "idbroker"-option, where the next ID is store in
the table 'ID_TABLE'. The entry for TURBINE_USER is correct. So I have
no idea, why it's not working like for all the other tables (the tables
created by myself).
Did you recompile the source for MySQL?
For 1.5, you can only use the binary distributables with HSQL.
If you want to use another database, and you want to be ale to add
records, then you need to recompile.
NOTE: with the 1.6 release Im working on, you won't need to recompile
for different database backends. Instead, just replace the torque-om jar
file. All of the torque-om jars will be prebuilt and provided with the
release.
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
