From: David L. (JIRA) <no...@at...> - 2006-05-29 14:23:20
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-668?page=comments#action_23189 ] David Leal commented on HBX-668: -------------------------------- Dear Christian, My suggestion doesn't have to complicate the hbm2dll, because all such definitions the user have to insert via property file, it was just the suggestion, you know better than me what is the best design for this feature. I am aware of that it could be complicated to consider all cases, that is why my suggestion was to at least allow the user to configure if the primary key definition could be generated via ALTER TABLE, so on the generated file will be easier to modify. Now you have to delete the primary key definition on each create table and add an ALTER TABLE for each primary key, with my idea you at least you don't have to delete the primary key definition on the create table. We use hbm2ddl for getting the schema in oracle syntax because on production we have Oracle but during developer process for the moment we use mysql. Then we process the generated hbm2dll file in order to fix all this details like tablespace, etc. Please could you be more explicit about your comment no <database-object> (I guess it is a new features on the mapping files), in our particular case we make some minimal modification on the *.hbm file in order to add the oracle sequence during the building process. Probably to add also on this node specific database information would be more complicaded than just modify the database script. > Additional configuration for hbm2ddl script generation > ------------------------------------------------------ > > Key: HBX-668 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-668 > Project: Hibernate Tools > Type: Improvement > Versions: 3.1.beta5 > Reporter: David Leal > > > Just to suggest some additional configuraiton for hbm2ddl script generation, for example: > - Adding possibility to configure if the primary key can be defined using alter table instead on the create sentence. > - The same for unique index. > - Adding possibility for configuring information not provided by the *.hbm files, for example tablespace information. For example on the configuration file, could be defined the tablespace information for each table/index, primary key, etc. > The alter table aproach is better for production database in order to add tablespace information, such configuration can't be set on the create table sentence. > Thanks in advance, > David -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |