This setting works fine if the database is empty, but if the tables are already created, i get error messages in the logfile.
Now the code still works fine so no problem, but getting [ERROR] written to the logfile everytime the programm is run is not something I want.

I would find it tedious to have to change the value in persistence.xml every time when i need either create or validate functionality. So maybe you can tell me if it is possible to manually initiate validation/creation.
OR you can tell me i can leave hbm2ddl.auto perpetually to create, because it causes no harm and there is a way to suppress those error messages without suppressing all hibernate related errors.


Also the information for the behaviour of create is not clear regarding the dropping of tables when the database is not empty, I'll quote your documentation:



some sources reported a deleting of tables, my experience is it does not delete the tables prior to creating, it does give me ERROR messages though as stated above.

Thanks already!

you could try update, but I really wonder if you would trust that on production databases, the only value I would ever recommend is "validate".

The class SchemaExport can be used to programmatically control DDL statements; which is callable from command line too as a tool; or there's an ANT task too, so you can automate this kind of jobs. Finally, people often play with "profiles" and deployment targets, using filtering (Ant or Maven) of the persistence.xml to insert the appropriate tokens.


isn't that exactly what the quoted documentation is stating? what's confusing?