Sounds like everything you describe is already implemented. Can you tell
what problems do you have using any of these features?
fedor.
> -----Original Message-----
> From: Jason Kary [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 31, 2001 1:18 PM
> To: [EMAIL PROTECTED]
> Subject: Torque Feature?
>
>
> Hi,
>
> I was thinking about adding the following features to torque and was
> wondering if anyone is working on a similar features:
>
> 1) The ability to generate a project-schema.xml file from an
> existing DB
> using TorqueJDBCTransforTask.java.
>
> This would be useful as we have a few projects that already have a
> schema defined. Some of the details in building this feature might
> include the ability to specify tables that are included, excluded, and
> read-only.
>
> 2) The ability to maintain many project-schema.xml files.
>
> I could not see an easy way to have xml files for two different DB's
> maintained. Please correct me if I am confused.
>
> 3) An automated development cycle. (I.E. Updating a schema
> definition->generate a new object model->dump existing tables->drop
> tables->create tables->add data to new tables with default
> value for new
> column.)
>
> The 'blue-sky' goal is to have a centralized schema.xml which will
> propagate changes to a database (dev, stage, prod) automatically.
>
>
> Thoughts?
>
> Take Care
> Jason Kary
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
