Re: EROraclePlugIn, migrations and reserved words
Re: EROraclePlugIn, migrations and reserved words
- Subject: Re: EROraclePlugIn, migrations and reserved words
- From: Don Lindsay <email@hidden>
- Date: Sun, 29 Nov 2009 13:39:33 -0500
I would discourage you from using reserved keywords for table
names, it will get you into trouble. if you are having problems with
SQL generation, you may end up having problems with your application
when the EOF is attempting to update/insert/or retrieve data.
To be safe, change the table name to users or theuser and leave your
class name as User so your code does not have to be modified.
Don
On Nov 28, 2009, at 11:49 AM, Jon Nolan wrote:
Is there a way to get the Oracle reserved words as table and
attribute names double-quoted in the generated SQL? I have a USER
table I'd rather not rename unless absolutely necessary.
The following is generated and fails:
CREATE TABLE USER(USER_ID NUMBER);
The following is legal:
CREATE TABLE "USER"("USER_ID" NUMBER);
I assume I would have the same problem post-migration with select/
update/delete statements.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden