I am planning on making some changes regarding id generation in BasePeer and
IDBroker. A couple things:
1. BasePeer contains some methods, getNextSequenceId, does anyone mind if
these methods are moved to IDBroker (or some other class that gets created
during the reorganization?)
2. When I first wrote BasePeer, I wrote it so that updates/inserts could be
made to several tables with one call to doUpdate/doInsert. I.e., if
Criteria contained column data for columns in 3 different tables and
doInsert was called, a row would be inserted into the 3 tables. Does anyone
think this is useful? Or does it just complicate the code? I personally
have never used the feature. And I could see that using BasePeer in this
way could lead to hard to maintain code. Would anyone object to removing
this feature?
3. I am planning to change IDBroker to use BigDecimal as its internal type
for the id. It would contain some convenience methods to return an int or
long as well. We need to do something about the use of int for object ids.
This should probably be changed to at least a long. Maybe it should be
abstracted as an oid object.
Thoughts?
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
