Date: 2004-08-22T20:06:21
Editor: ScottEade <[EMAIL PROTECTED]>
Wiki: DB Torque Wiki
Page: NextRelease
URL: http://wiki.apache.org/db-torque/NextRelease
A couple of the listed items have been addressed in cvs even for 3.1.1
Change Log:
------------------------------------------------------------------------------
@@ -15,19 +15,14 @@
== Further Suggestions ==
- * Update the handling of PostgreSQL sequences for version 7.3 (see:
["PostgreSQLFAQ"])
- * If no id-method-parameter elements are declared then the sequence should be
named table_column_seq and the sequence does not need to be explicitly created or
dropped.
- * Perhaps use the current behaviour if id-method-parameter elements '''are'''
declared so as to cater for PostgreSQL versions prior to 7.3.
- * Correctly generate index and unique constraint names for PostgreSQL (see:
["PostgreSQLFAQ"])
* 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).
- * IMHO the Torque Maven plugin is very difficult to use due to varying versions of
Maven and Torque (I had to actually hack the plugin to get things working). In
particular I think we really need to support:
- * Multiple versions of Torque.
- * The ability to add further versions outside of the Maven release cycle.
* Provide for an encoding attribute on the database element - to be used in create
database statement for PostgreSQL (and presumably others).
-- ScottEade 2003-10-09
+
+ * The jdbc target (torque:jdbc goal in Maven-speak) needs to generate the correct
DDL SQL for PostgreSQL serial columns (see: ["PostgreSQLFAQ"]) -- ?ScottEade 2004-08-20
----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
