CLOB in FrontBase gives null in search
CLOB in FrontBase gives null in search
- Subject: CLOB in FrontBase gives null in search
- From: Thomas <email@hidden>
- Date: Wed, 7 Sep 2005 13:05:52 +1000
I have been using a code-generated query to FrontBase that has been
working for years, built out of things like:
...
format += "title caseInsensitivelike %@";
args.addObject(keyword);
format += " or contentHTML caseInsensitivelike %@";
args.addObject(keyword);
format += " or keywords caseInsensitivelike %@";
args.addObject(keyword);
...
I have just changed the contentHTML field from varchar to clob,
because some of our customers user Word to generate their content and
it gets really big. That works fine for most things, but the query
above now fails with:
Semantic error 218. NULL not allowed here.
because the SQL generated is (using a keyword "junk"):
t0."TITLE" LIKE '%junk%' COLLATE INFORMATION_SCHEMA.CASE_INSENSITIVE
OR t0."CONTENTHTML" LIKE NULL COLLATE
INFORMATION_SCHEMA.CASE_INSENSITIVE
OR t0."KEYWORDS" LIKE '%junk%' COLLATE
INFORMATION_SCHEMA.CASE_INSENSITIVE
So is it true I can't do case insensitive like with FrontBase CLOB
using WebObjects?
Any suggestions would be welcome.
I've tried changing the model to varchar while leaving the database
CLOB, which works for most things, but fails the query above because
the field is not of type text.
_______________________________________________
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