Problem 1: How do I specify a unidirectional between two tables?

 

Solution: add the unidirectional="true" attribute to the <foreign-key> tag

 

Problem 2: How do you map many-to-many between table such as user and group
map to user_group without having torque create the classes for the
user_group table? 

 

Solution: Specify joint-table="true" in the <foreign-key> tag in the user
and group tables

 

The implementation of the above problems should be at least like the
relationship in EJB CMP 2.0

 

Problem 3: How do you separate the business object and business object
manager into separate classes so that your object model increases decoupling
between interface and implementation?  Currently, BaseXYZ.jave contains both
the business object functionality such as getter/setter and business object
manager functionality such as save, update, delete, etc... 

 

Solution: The BaseImpl.java class should contain only the getter and setter
for the business object and nothing else... and it should be implementing
the Base.java interface.  In addition, the BaseImplManager.jave should have
all the manager functionalities and it should be implementing the
BaseManager.java interface

 

Problem 4: If a table contains only a single primary field then the
Base.java classes should return the actual java data type such as Long or
String and not NumberKey or StringKey or anything else on the primary field.


 

Problem 5: Torque should allow the user the specify the naming convention
and data type conversion somewhere so that the user can be pick and
choose...

 

Also, the current security model needs to change and I am in a process of
doing that.  I would love to see what you've out there for the proposed
functionalities before I go ahead with my implementation.

 

Hai Hoang

 

 

 

 

 

 

 

Reply via email to