Date: 2005-02-23T09:59:19
Editor: ThomasFischer
Wiki: DB Torque Wiki
Page: NextRelease
URL: http://wiki.apache.org/db-torque/NextRelease
Sorry, I misunderstood one of the further suggestions, undid some changes.
Change Log:
------------------------------------------------------------------------------
@@ -8,7 +8,7 @@
* improve the generated ojb model
* 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 some basic schema support at runtime and generate 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)
@@ -17,7 +17,8 @@
== Further Suggestions ==
- * 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.
+ * 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.
* 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
