On 06 Jun 2001 12:37:27 -0700, Jon Stevens wrote:
> on 6/5/01 4:49 PM, "Bruno Unna" <[EMAIL PROTECTED]> wrote:
>
> > Is there a recommended procedure to make DB structural changes to an
> > application once it has been generated, or even once the database has
> > been populated? A sort or backup/restore procedure (I know that for
> > severe changes to the DB structure it is nonsense, but for slight or
> > gradual ones, it is not).
>
> Create a file with alter table statements in it.
But doesn't that imply I have to give up the benefits of using torque? I
would love to make the structural DB changes in the
<project-base>/WEB-INF/build/project/<project-name>-schema.xml file.
And if it is not directly possible, what would be the best way to
implement it? I've been thinking of adding a couple of targets to the
build.xml ant file, one for saving and one for (perhaps just trying) to
restoring the information.
In an ideal world, the DB design would be ready and definitive before
the actual coding of the business rules. Problem is: this is not an
ideal world, so the very skeleton of the data to be used by an
application is due to changes in advanced stages of development...
--
"Create like a god, Bruno Unna <[EMAIL PROTECTED]>
command like a king, Internet de Alta Calidad
and work like a slave." Red Hat Certified Engineer
Kawasaki PGP public key available
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
