db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ojb-...@db.apache.org
Subject [DB OJB Wiki] Updated: BestPractices
Date Tue, 11 May 2004 15:17:08 GMT
   Date: 2004-05-11T08:17:08
   Editor: 63.80.251.77 <>
   Wiki: DB OJB Wiki
   Page: BestPractices
   URL: http://wiki.apache.org/db-ojb/BestPractices

   reformatting to make it eaiser to read

Change Log:

------------------------------------------------------------------------------
@@ -30,7 +30,7 @@
 [[BR]]1. use (modified) reverseDB to generate VOs and repository_user.xml for tables and
views in DB
 [[BR]]2. modify VOs, and repository_user.xml to reflect our logical mapping of the tables
(compositeVOs)
 [[BR]]3. verify basic CRUD for VO(BaseDAO handles Create, update, insert, findByVO, findbyPK
for any mapped object)
- (optional) build specific DAO if BaseDAO isn't good enough
+[[BR]]  (optional) build specific DAO if BaseDAO isn't good enough
 [[BR]]4. BusinessDelegate objects get handle to DAO through a factory
 [[BR]]5. BusinessDelegate controls transaction when it needs to
 [[BR]]6. OJB query and Criteria are wrapped in our QueryVO object so that biz layer doesn't
know about OJB 
@@ -44,8 +44,9 @@
 [[BR]]- We use SequenceManagerNativeImpl to grab DB2 created Identities
 [[BR]]- Created a conversion Boolean2CharYN (for converting a single char 'Y' or 'N' in DB
to a boolean
 [[BR]]- We had to create our own PlatformCustDb2Impl because the identity query(in RC5) did
work with DB2 7.x 
+[[BR]]- Set Auto-commit ="2" because DB2 doesn't like nested commits
 
 open issues:
 [[BR]]- queryBySQL fails on DB2/websphere 4 when executing the same query twice (we coded
a workaround)
 [[BR]]- we have a few 1-1 parent child mappings and we want the parent to contain a child
-[[BR]]- we keep history in our tables, so we often have a date as a primary key, but we don't
know the exact date when we do a join, but we want to join on the most current date. this
is a problem for 1-1
+[[BR]]- we keep history in our tables, so we often have a date as a primary key, but we don't
know the exact date when we do a join, but we want to join on the most current date. this
is a problem for 1-1 mappings

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message