Re: Strange behavior of Derby database. SQL generation (SOLVED)
Re: Strange behavior of Derby database. SQL generation (SOLVED)
- Subject: Re: Strange behavior of Derby database. SQL generation (SOLVED)
- From: "Mr. Pierre Frisch" <email@hidden>
- Date: Tue, 5 Feb 2008 12:32:13 -0800
I would still log a bug, please. This may be something we can fix in
the plug-in.
Pierre
--
Pierre Frisch
email@hidden
On Feb 5, 2008, at 12:18, Sergio Sánchez Maffet wrote:
After intensiv reading of the derby docs I found the reason. It
happens because derby alway uppercases all unquoted identifiers. The
SQL generation in WOLips puts quotes around the identifiers, turning
on case sensitivity in derby during creation of the tables. The
generation of SQL in SQLExpression later accessing the database uses
unquoted identifiers. They are uppercased by derby and checked
against the case-sensitiv stored ones, which where in my case
lowercase ones. Tricky.
The workaround is simple: Use always uppercase identifiers in your
model file.
On 05.02.2008, at 20:16, Sergio Sánchez Maffet wrote:
The table name in the log submitted in my prior post should be
TESTA and not CONTENT. This is only a copy paste failure... and
does not mean, that a have misspelled the table name! The problem
is still there...
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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