|Can I "just adjust" the schema manually in database, using statements like
|"ALTER TABLE ADD COLUMN ..." or does JAWS maintain a number of assumptions
|somewhere about what the schema is, that will then become inconsistent?
You need to provide an object that reflects that schema either 1-1 name
mapping or jaws.xml to specify the mapping.
|Do I have to stop all services for this or is there a way to ask the "hot"
|deployment service to look in for a particular "script" in a .jar or .ear
it can be done hot, you just need to 'redeploy' the correct bean.
|file, that is, a class to instantiate, for example "ConvertDb2to3()" (with
|the default constructor), prior to installation, and in which I can use an
|appropriate set of statements to adjust the schema.
Yes, again, for the 3rd time, we do not manage your schema, we manage
objects that reflect your schema.
Redeploy the bean and you are all set.
Only at deployment time, if the table doesn't exist, will we create a schema
for you as a *convenience*. If the schema exists, and you come from the DB
world (poor soul), we don't do anything, so just supply the good bean and
basta.
|If such is the case, I can definitely live without "automatic schema
|upgrades", which would be a "nice to have", but not a show stopper.
Redeploy the correct bean.
Say you add a entry with "newIntStuff" you need a field with "newIntStuff"
you don't specify anything else, will work. but *you* need to specify that
new field and new object
DB guys....
marc
|
|
|--
|--------------------------------------------------------------
|To subscribe: [EMAIL PROTECTED]
|To unsubscribe: [EMAIL PROTECTED]
|Problems?: [EMAIL PROTECTED]
|
|
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
