You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the validation is done by the underlying database. You will get a persistence-exception when you try to insert null in a non null column or a too long value in a varchar column.
There is a special validation for (unbounded) clobs: #3343
If you want to do bean validation, you might take a look at hibernate bean validator
@rPraml Hello, what I mean is that in JPA, you can configure the DDL strategy as update/create/dropCreate to decide whether to update the table structure, create tables, or drop and recreate tables when the project starts. I would like to know how to achieve this in Ebean. Currently, I only see that tables can be created by configuring whether to execute DDL.
Note: These scripts are generated "offline" from your code base. Ebean does NOT "look into the database" and tries to migrate it. So if you have manually altered a table or added an index, you might get problems later, because ebean does not know about this.
You can control the generation with @DbMigration annotations or add also custom scripts
No description provided.
The text was updated successfully, but these errors were encountered: