Hi Marc! But I think this guy has a point in what he is saying. If jBoss
offers a JAWS solution where it can create tables if not existent during
deploy then I think it was really nice if it could checkout any changes
in the db schema during redeploy of a bean and:
1) Only give warnings about it or
2) Genereate a script that the user may use to update the db manually or
3) Actually make the update of db schema if and only if the user
confirms this after he has seen the db script.
But I also understand your idea of that jBoss will not manage the db
schema but it would be possible to do and i think that many would like
it or...?
/Lennart
marc fleury skrev:
>
> |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]
--
mailto:[EMAIL PROTECTED]
http://www.benefit.se/english
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
