db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From torque-...@db.apache.org
Subject [DB Torque Wiki] Updated: NextRelease
Date Wed, 23 Feb 2005 17:39:11 GMT
   Date: 2005-02-23T09:39:11
   Editor: ThomasFischer
   Wiki: DB Torque Wiki
   Page: NextRelease
   URL: http://wiki.apache.org/db-torque/NextRelease

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -2,25 +2,22 @@
 
 == Planned for the next release ==
 
-Note that development for the next release in CVS can be found under the Branch TORQUE_3_1_BRANCH,
but some of the items listed here have been done in HEAD.
-
- * remove the old, deprecated and buggy !ConnectionPool - '''done''' HEAD
- * drop support for idMethod = sequence | autoincrement - '''done''' HEAD
+ * remove the old, deprecated and buggy !ConnectionPool - '''done''' 
+ * drop support for idMethod = sequence | autoincrement - '''done''' 
  * move all db specific stuff from the generated classes to the base classes (so you don't
have to regenerate the modell for different dbs)
  * improve the generated ojb model
- * add scale attribute for columns - '''done''' HEAD
- * Add support for outer joins - '''done''' TORQUE_3_1_BRANCH
- * Add some basic schema support - '''done''' TORQUE_3_1_BRANCH
+ * add scale attribute for columns - '''done''' 
+ * Add support for outer joins - '''done''' 
+ * Add some basic schema support, including override of database name at generation time
- '''done''' 
  * add domain element to schema.xml (name, type, javaType, size, scale)
    * the domains can be reused in any column
    * this allows to map jdbc types to domains and solves the problem with definitions like
BIGINT = NUMBER (20, 0)
- * add platform package to replace db.prop files (inheritence is your friend ;-)
+ * add platform package to replace db.prop files '''done'''
  * backport sql generation for the generator from commons-sql (inheritence is your friend
;-)
 
 == Further Suggestions ==
 
- * Allow override of database name at generation time
-   * If specified the torque.database.name property should be user rather than name attribute
of the database tag.  This would make it much easier to handle multiple instances of an application
on a single system, e.g. dev and test database instances being generated from a single schema.
+ * If specified the torque.database.name property should be user rather than name attribute
of the database tag.  This would make it much easier to handle multiple instances of an application
on a single system, e.g. dev and test database instances being generated from a single schema.
  * Is it just me or are a number of the torque properties required to be declared outside
of the file referred to in torque.contextProperties?  Could the Torque Maven plugin read the
properties in as well, making it so that project.properties need only define torque.contextProperties?
 This would make it much easier to handle multiple application instances built from the same
environment (I run a number of filters across my properties file to customise it for the application/database
instance I am generating before I execute the generator).
  *  Provide for an encoding attribute on the database element - to be used in create database
statement for PostgreSQL (and presumably others).
 

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


Mime
View raw message