> Perhaps what Torque needs is a seperate database-schema.xml and > db-om-mapping.xml that would seperate the db and om code? I realize this > is not a v3 thing, but would something like this make sense? I would > think it almost necessary if the possiblity of becoming OJB's > forward-reverse tool becomes more likely.
I think the db-om-mapping.xml thing might happen. Somewhere out of Torque/OJB/commons-sql/db.apache.org a new project solely devoted to forward/reverse generation of SQL stuff will form. I imagine it will use some minor variation on the current Torque schema (minus any Java-specific stuff that has snuck in). Upon that, hopefully they'll be an easy way to extend the schema to handle OJB/Torque/etc.-specific settings. Whether this is done via properties, the schema itself, or a separate XML file as you brought up, is still up in the air. I haven't looked at OJB's schemas close enough yet, but it'd be pretty cool to have an OJB -> SQL-only schema and SQL-only -> OJB generation. Perhaps if Torque donates it's schema to this SQL-only project, it could (in v4) start over with a new, OM-only schema (perhaps this is what you suggest) that could then be mapped Torque -> SQL-only and in reverse, SQL-only -> Torque. This is cool stuff; just wish I had more time right now to fool around with it. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
