{"id":3734,"date":"2011-05-04T00:49:07","date_gmt":"2011-05-03T19:19:07","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=3734"},"modified":"2011-05-04T00:52:19","modified_gmt":"2011-05-03T19:22:19","slug":"grails-domain-class-and-ddl-sql-file-using-schema-export","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/grails-domain-class-and-ddl-sql-file-using-schema-export\/","title":{"rendered":"Grails domain class and DDL sql file using schema-export"},"content":{"rendered":"

While debugging a domain and its database schema I found an interesting grails command line Gant script<\/code>: schema-expor<\/strong>t<\/a>.<\/p>\n

One of the great Grails command line Gant script<\/code> to generate SQL scripts(DDL) <\/code> which is executed against your database to model your grails domain<\/code>. You can control the environment and the output file to generate the SQL script. Without going into much details lets see an example. Here is the only domain in my grails project<\/code> :<\/p>\n

[groovy]
\nClass Person{
\n\tString name
\n\tInteger age<\/p>\n

static hasMany=[emails:String]
\n}
\n[\/groovy]<\/p>\n

And here is the script I used<\/p>\n

[shell]
\ngrails schema-export
\n[\/shell]<\/p>\n

Here is the content of generated DDL file which is created in project’s target folder with name ddl.sql by default(obviously data source settings of Development environment).<\/p>\n

[sql]
\nalter table person_emails drop foreign key FKADA31081669C99A9;
\ndrop table if exists person;
\ndrop table if exists person_emails;
\ncreate table person (id bigint not null auto_increment, version bigint not null, name varchar(255) not null, primary key (id)) ENGINE=InnoDB;
\ncreate table person_emails (person_id bigint, emails_string varchar(255)) ENGINE=InnoDB;
\nalter table person_emails add index FKADA31081669C99A9 (person_id), add constraint FKADA31081669C99A9 foreign key (person_id) references person (id);
\n[\/sql]<\/p>\n

You can also specify the environment (e.g. prod<\/code>) whose data source<\/code> settings will be used to generate DDL and output to a different file(e.g. prodDDL.sql<\/code>) like :<\/p>\n

[shell]
\ngrails prod schema-export prodDDL.sql
\n[\/shell]<\/p>\n

Full documentation ca be found here schema-expor<\/strong>t<\/a>.<\/p>\n

Hope it encourage you to read the Grails documentation<\/a><\/strong> in spare time to find and share hidden features of grails<\/strong>.<\/p>\n

~~~~Cheers ~~~~<\/p>\n

Bhagwat Kumar
\nbhagwat(at)intelligrape(dot)com<\/p>\n","protected":false},"excerpt":{"rendered":"

Grails Schema-export GANT script to generate DDL sql file of the grails project domains.<\/p>\n

eg.
\n grails prod schema-export myProd.sql<\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":15,"footnotes":""},"categories":[7],"tags":[563,562,561,559,4840,560,558],"class_list":["post-3734","post","type-post","status-publish","format-standard","hentry","category-grails","tag-datasource","tag-domain-ddl","tag-environment","tag-gant-script","tag-grails","tag-schema-export","tag-sql"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t