When I use the default sequence manager, it requires an OJB_HL_SEQ table, and key generation gets a little sloppy when adding or deleting from outside OJB. Here's what I'd like to use:
1) A sequence manager that will use mySQL's built in keying. In other words, I'd like to set the ID field of my (new) object to null, then store the record, and then check to see what ID it got.
2) A sequence manager that does not need additional tables to operate. I sometimes deal with situations where I have only SELECT, UPDATE, DELETE access on the tables I'm utilizing... and I cannot create new tables for OJB to utilize.
The documentation seems to suggest that there is a solution to these issues, but I can't find examples to try out. So far though, I love the convenience of OJB. Great work!
Thanks, Aaron Longwell
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]