Re: Case sensitivity with PostgreSQL and WO5.x
Re: Case sensitivity with PostgreSQL and WO5.x
- Subject: Re: Case sensitivity with PostgreSQL and WO5.x
- From: Stirling Olson <email@hidden>
- Date: Tue, 23 Nov 2004 13:55:46 -0700
I think that gem came from page 220 in "WebObjects for Mac OS X" by
Joshua Marker. This book is a great starting book for WebObjects and
useful reference guide. It doesn't cover many of the
intermediate/advanced topics in WO like dealing with the object store
but is a great way to get started. For the more advanced stuff
"Practical WebObjects" by Charles Hill and Sacha Mills is invaluable.
Great book.
Those two books and the Omni WebObjects-dev list are my main
references. Omni is at:
http://www.omnigroup.com/developer/mailinglists/
Best Regards,
Stirling
On Nov 23, 2004, at 1:01 PM, Mez wrote:
Hi Stirling,
Sterling idea (if you'll pardon the no doubt well worn pun) ;-)
Works a treat. Out of curiosity, and for my own education, where did
you find out about that little gem? I'd scoured the documentation from
Apple, as well as several WO books.
Thanks and BR,
Mez
On 23 Nov 2004, at 18:49, Stirling Olson wrote:
Whoops. I'm missing an i in there. Should be:
caseInsensitiveLike
There is no button in the EO Modeler but you can just type this in
wherever you were using 'like'.
Hope that helps.
-Stirling
On Nov 23, 2004, at 11:47 AM, Stirling Olson wrote:
Like is case sensitve. You should substitute 'CaseInsensitveLike'
for 'Like' in your EO model and/or qualifiers.
-Stirling
On Nov 23, 2004, at 11:20 AM, Mez wrote:
Hi,
Has anyone had problems with LIKE searches yielding case sensitive
results?
My WOApp used to work fine with Openbase, but with pgsql I now have
to be aware that searches are case sensitive - which is not
desired/desirable at all in my case. Even if it is SQL92/99
compliant.
I've compiled version 7.4.6 on MacOS X 10.3.6 and also built Kenny
Leung's generously provided EOModeler plugin and the accompanying
framework, and otherwise PostgreSQL works fine.
As a workaround, I've tried to use raw SQL in EOModeler, when
setting up a fetch specification, but although this seems to yield
the correct behaviour in EOModeler, it causes syntax errors in WO
when running the application.
I've also tried amending the plugin and framework to use different
escape characters, but I get the same problem.
Any solutions/ideas?
TIA,
Mez
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
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:
email@hidden
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:
email@hidden
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