Hibernate version: 3.2.6

Hi all,

I'm trying SchemaUpdate tool via directly calling it by code.

I'm trying with a very simple example, ONLY ONE TABLE, the classic table Person.

So, I've seen that if I add a column, then launching SchemaUpdate, the tool sees new property/column then executes alter table adding new column.

But, if on the contrary I delete that just added property, deleting it either from Person.java either from Person.hbm.xml, the relaunching SchemaUpdate, it seems that it doesn't execute the alter table to delete the column from the table.

Please, can you explain me the reason?

Should SchemaUpdate update every change? Or are there some changes that SchemaUpdate is not able to reproduce?

Thanks in advance, best regards
Gamby

schemaupdate does not know about your previous model thus it cannot know if it should delete that extra column. schemaupdate is additive not destructive ;)

Scuse me but this answer doesn't resolve the problem.

There is a real problem, that is, an application in which, version after version, its database is changed, where these changes could be either new columns either some column deletion....
SchemUpdate is unusable

I have to design a mechanism with jdbc and with sql scripts that I deploy with my app and that they are executed on the first execution of the new just installed version performing updating work...

Any other hint?

Thanks in advance,
Gamby

Correct, patches resolve problems.



Yes, but schemaupdate was never intended to be used for migrating prod systems automatically.



For development it is rather useful.



Yes, so create a delta script and execute it.

The solution for this is not schemaupdate but more something like Migrations as known in Rails. I always wanted to do a Hibernate Migrations API but never had the time to do it....any takers ?