"When I saved a new class with a cascade-update collection, OJB would assign the same primary key ID to every member of the collection and save every member of the collection as though it was the same object. Therefore, I'd end up with one row in a database table instead of 10, with the values of the row reflecting the last member of the collection that was saved."
--Gareth.
O'brien, Tim wrote:
I think all programmers have those days when they spend five or six hours
trying to debug a problem that just won't go away ONLY to discover that
they've typed something in wrong.
I'm trying to compile a list of the top n gotchas one can run into with OJB
- here's the first one...
1. If you errantly type in "primary-key" instead of "primarykey" in a table
with a composite primary key you will run into terrible troubles trying to
update any rows.
Does anyone else have any ideas?
The purpose of this list is to give people a quick reference to check if
they are trying to debug an OJB related issue and they running out of
patience. I might help to have a list of very common errors, so people
could refer to a certain list before posting to a mailing list, etc.
Thanks in advance.
--------
Tim O'Brien W 847-574-2143
M 847-863-7045
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- ------------------- Gareth Cronin Analyst/Programmer Kiwiplan NZ Ltd Ph 2727622 x854 -------------------
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
