hi i'm using the latest torque with mysql and defaultIdMethod="native".
this generates for primary keys like <column name="ID" type="INTEGER" required="true" autoIncrement="true" primaryKey="true"/> this SQL: ID INTEGER NOT NULL AUTO_INCREMENT ok, so far so good, but i always get this warning: IDBroker is being used with db 'MYDB', which does not support transactions. IDBroker attempts to use transactions to limit the possibility of duplicate key generation. Without transactions, duplicate key generation is possible if multiple JVMs are used or other means are used to write to the database. i don't really have to worry about it when using "native", do i? can i or should i turn the IDBroker thing off? the next problem is creating objects connected with foreign keys. e.g. if i create a new object Artist and call save() it does not know it's own primary key yet, since mysql decides about the value, right? because when trying to tie it to another Website (they are connected via a m:n relationship) and saving this i get java.sql.SQLException: General error: Column 'ARTIST_ID' cannot be null if i create artist and website first, retrieve them into new objects, create the relationship and save then it works, but this is not very convenient. especially since i search for them by one of the other attributes (name) which is _not unique_, so it works in my small test setup, but: isn't there a bulletproof way to get the pk of the object just saved? bye fabian -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
