can SchemaExportTask generate quoted identifiers at output?

merge_radu · **Joined:** Fri Mar 04, 2005 3:00 pm **Posts:** 14

Hello,

I use schemaExport to generate my sql file and it works fine. A part of my output looks like this

Code:

create table WebOfferRequestParamsTable (
   ID int not null,
   webProbeID int not null,
....
 

problem is, when I excute this file with the ant task sql, everything is coverted into uppercases in the dataBase. In order to have the case preserved in th dataBase I need to have names quoted in the sql file, like the following

Code:

create table "WebOfferRequestParamsTable" (
   "ID" int not null,
   "webProbeID" int not null,
....
 

is there a way to make schemaExport generate my sql file with quotations included ?

thanks

max · **Posted:** Sun Mar 27, 2005 9:55 am

yes use qoutes in the hbm.xml (backticks will be converted to dialect specific quotes - see doc for examples)

merge_radu · **Joined:** Fri Mar 04, 2005 3:00 pm **Posts:** 14

the problem is the fact that i generate my mappings with xdoclet and
for many properties I am happy with the name of the attribute and write just
@hibernate.property

is there a solution to this? maybe a flag to set to hibernatedoclet or schemaExportTask ?...just asking

max · **Posted:** Sun Mar 27, 2005 12:17 pm

then dont quote names that are fine- only quote those that you want "forced" into the database.

merge_radu · **Joined:** Fri Mar 04, 2005 3:00 pm **Posts:** 14

I think I didn't made myself clear. for example i have the following code :

Code:

/**
     * @hibernate.property 
     * @return
     */
    public Integer getRequestType()
    {
        return requestType; 
    } 

this come into the mapping file like

Code:

 <property
......
            column="requestType"
        />

instead of

Code:

column= "`requestType`"

which is what i need in order to preserve case;

max · **Posted:** Sun Mar 27, 2005 12:36 pm

then use the xdoclet for specifying the column name.
yes - its redundant but that is what you would need to do it.

btw. why do you want the case preserved for all costs in the db ?
most dbs are case insensitive so it doesnt matter. Is it just for style ?

merge_radu · **Joined:** Fri Mar 04, 2005 3:00 pm **Posts:** 14

well, you could say that is just for style :)
i like to see things clear
thanks for the answers