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: TorqueFuture
Date Tue, 21 Dec 2004 10:07:24 GMT
   Date: 2004-12-21T02:07:24
   Editor: ThomasFischer <fischer@seitenbau.de>
   Wiki: DB Torque Wiki
   Page: TorqueFuture
   URL: http://wiki.apache.org/db-torque/TorqueFuture

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -6,17 +6,17 @@
 
 == General ==
 
- * Better documentation from the beginning. Maybe drop xdoc in favor of an easier to use
format?
+ * Better documentation from the beginning. Maybe drop xdoc in favor of an easier to use
format? (tfischer)
 
 == Torque Runtime ==
 
  * Get rid of the static Peer classes. (hps)
 
- * Get rid of Village. (hps)
+ * Get rid of Village. (hps,tfischer)
 
- * General SQL schema (database namespace) support. (hps)
+ * General SQL schema (database namespace) support. (hps,tfischer)
 
- * Defined datatypes for SQL columns and tables. (hps)
+ * Defined datatypes for SQL columns and tables. (hps,tfischer)
 
  * Introduce a some sort of "handle" onto a data source / table collection, allowing things
like defined initialization, setting default parameters (similar to Hibernate Session?) (hps)
 
@@ -24,13 +24,21 @@
 
  * Build a pluggable criteria system using a generator (connected to the "handle" object
to create a criteria and an evaluation method to get the query / select string) (hps)
 
- * (Maybe) split up the Criteria into an Insert / Select / Delete criteria (hps)
+ * (Maybe) split up the Criteria into an Insert / Select / Delete criteria (hps,tfischer)
 
  * Build a unified Transaction system, which is able to use different transaction types thus
allowing the usage of transactions managed by a container (hps)
 
- * Keep the "simple" approach that made Torque fast and versatile: Don't try to rebuild Hibernate.
No  generic object -> SQL mapper, just a table schema representation in SQL (hps)
+ * Keep the "simple" approach that made Torque fast and versatile: Don't try to rebuild Hibernate.
No  generic object -> SQL mapper, just a table schema representation in SQL (hps,tfischer)
 
- * No implicit caching (maybe pluggable). Use JCS? (hps)
+ * No implicit caching (maybe pluggable). Use JCS? (hps,tfischer)
+
+ * Improve handling of 1:n relations: Add support for deleting related objects (tfischer)
+
+ * (Maybe) handle n:m relations automatically ? (tfischer)
+
+ * add support for "forcing" developers to use transactions (e.g. no background read, no
save methods without connection arguments). Use a switch in the configuration for this. (tfischer)
+
+ * look into how related objects can be linked tighter, but retain the current save-through
behaviour. Perhaps be able to modify save-through on runtime ? (tfischer)
 
 == Torque Code generator ==
 

---------------------------------------------------------------------
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