I will take a stab though (disclaimer, I am just a user and part time OJB doc writer).
On Thursday, August 28, 2003, at 02:37 PM, Terry Brick wrote:
I'm using OJB 1.0rc4, MySQL, SequenceManagerNativeImpl for the sequence manager and am using PersistanceBroker.
I have never used it with MySQL, uh oh.
#1 --- Whenever I try to store an object that has references to another class, OJB is requireing that the referenced class have an autoincrement field. All I
This is required for optimistic locking (alternately I believe a date or timestamp field works for this), but shouldn't be required for all references without use of optimistic locks. It *does* require a primary-key field (I believe, am running from memory here and I always have a primary-key specified anyway) which, as the case may be, is always auto-incremented. I need to check and verify if auto-increment is required for any relation, but that doesn't sound right...
<snip>do to make it work is set autoincrement="true" and it's fine... even though it may NOT be an auto incrmement field. SO FAR, this has not been a big issue, but I can't help but think it's going to back and bite me. I've posted the error message before,
It looks like you are using database field names your reference-descriptors and collection-descriptors. These should be java object fields, not database fields.
Take a look at the http://db.apache.org/ojb/howto-use-anonymous-keys.html anonymous key tutorial (I think the code -> metadata is clearer there) at the class-descriptors.
Any chance you can post your class code? If not I can whip together a demo of a working on doing approximately what you ask next week (am leaving for a short vacation myself tonight). Sorry no one has gotten back to you more quickly.
-Brian
ps: any way you can turn off the line chopping in your mua? It makes your mail difficult to read.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
