Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-torque Wiki" for 
change notification.

The following page has been changed by ThomasFischer:
http://wiki.apache.org/db-torque/NextRelease

------------------------------------------------------------------------------
- = Development information =
+ = Torque 4 =
+ 
+ The plans of the Torque development team for Torque 4 are summarized below. 
Please change the consensus list only after discussing your proposal on the 
Torque developers list.
+ 
+ Consensus is to do the following things:
+ 
+  * Next main version should be 4.0.
+ 
+  * Simplify the repository structure: No svn externals any more
+ 
+  * Kick out village
+ 
+  * Change the way to handle non-record-type queries (we used village for that 
until now)
+ 
+  * Criterias should not be modified any more inside queries.
+ 
+  * Disentangle Query description and SQL creation code.
+ 
+  * Use the Criteria object only to hold query data and another object to hold 
update data. Criteria should not extend Hashtable any more.
+ 
+  * Use a column object to hold the column name in the runtime instead of 
Strings
+ 
+  * Support views
+ 
+  * Use a custom velocity renderer to have nicely trimmed generated code.
+ 
+  * Have a non-static version of Peer classes. Implementation details are 
under discussion.
+ 
+  * Evaluate whether ddlutils can be used for some generator tasks
+ 
+ Under discussion:
+ 
+  * Switch to Maven 2 as build system.
+ 
+  * Make the generator more generic.
+ 
+  * Support primitives in data objects
+ 
+ Problematic:
+ 
+  * Use Java 5 style generics and enumerations. The problem is that Java 5 
code does not run on jdk 1.4
+ 
+ In a later version of Torque 4:
+ 
+  * Support for object level views
+ 
+ In a later version of Torque 4, under discussion:
+ 
+  * Support for lazy loading
+ 
+ ----
  
  == Further Suggestions ==
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to