Grails is really easy to get started with on green-field projects because the domain model defines the database schema, so you don't have to worry about that side of things.
In that case, you have to carefully map the domain classes yourself.
If you have a large schema, that could take a while.
You can do that with the following commands: Every time you make a change to your schema, such as adding a field to a domain class, creating a new domain class, etc., you'll need to create and run a migration.
After making a schema change, you'll want to issue the following command to generate a new migration to be run: line in your initial changelog file.
Nut Data' on field 'idd': rejected value [123456-1234]; codes [sps.
It seems that you are saving a duplicate object with the same idd. def gotten From DB = The Object.get( ) ; //for example def updates Object = new Make New Object From JSON( request ) ; // this one contains the updates // either check property by property or just update all properties // whatever is more efficiente or if you don't care.You will need to remove any “db Create” lines from grails-app/conf/Data Source.groovy.This is done to prevent grails from attempting to make changes to the schema on its own. Another option is delete the old object and insert the new one: but this must be performed in a [email protected]: I think you should re-check the constraint of the domain class (or better, post the domain class structure so we can all check). @Hanu Athena: well, the typical way is to get the object IN DATABASE out and change its properties according to your new object, then call save.When developing a web application, it is often important to make structural changes to the database backing it, as well as keep track of these changes and make it easy for other developers to make the same ones. They give you this support and functionality, as well as many other things such as rolling back database changes and generating data for newly created non-nullable columns.