+1 good idea david
+1 add an opt-in flag
-dain
On Nov 17, 2005, at 11:25 PM, Aaron Mulder wrote:
My only concern is that executing SQL scripts not be the default
behavior for an application. As a developer I generally prefer to be
the master of the SQL and not have the server doing things
+1 to both ideas. For production deployments the DBAs generally don't allow
servers or applications to arbitrarily create databases and tables. For
development / testing this is an improvement that with an opt-in flag would be
excellent.
+1 to both
Aaron Mulder wrote:
My only concern is
Sometimes an application needs some database tables in order to run.
We don't have much support for helping with this. We have the juddi
server, with a script that is run from jelly code in modules/assembly,
and we have some work to generate scripts for cmp entity beans, but no
automated way
My only concern is that executing SQL scripts not be the default
behavior for an application. As a developer I generally prefer to be
the master of the SQL and not have the server doing things for me, and
I think that's especially important as you look at non-developer uses.
But if we have a
