Re: EO & MySQL tedious error
Re: EO & MySQL tedious error
- Subject: Re: EO & MySQL tedious error
- From: Fabrice Truillot <email@hidden>
- Date: Thu, 11 Sep 2003 16:02:15 +0200
On Mercredi, sep 10, 2003, at 16:09 Europe/Zurich, Jonathan Rochkind
wrote:
I'm guesing your problem is that 'key' is a reserved word in MySQL,
that's why it needs to be surrounded by quotes?
Precisely. :) I've the same problem with MySQL 3 or 4. PostgreSQL works
fine.
Ideally, you'd change the name of that column, to not run into this.
If you can't do that though....
Too much of old PHP code to change, test and review. Not an option if
there is another way (and there is :) ).
I think you can just define the 'external name' of the attribute, in
EOModeler, to have quotes around it. That is, instead of:
key
In EOModeler, the external name is:
"key"
With the quotes. That should do it for you, and EOModeler should use
quotes every time it generates SQL involving this attribute.
You're almost right ! I've changed the external name from key to `key`
and voilC . Single and double quotes do not work (SQL errors, even on
read operations).
Many thanks for your quick answer, you were very helpful.
Fabrice Truillot, MiS c1c$g4 c.d::
www.meninsilicium.com
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.