InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples
FAQs

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Hi Joseph

I think this is what I would expect to happen. String literal parsing
happens very early on during execution of a SQL statement. The "\" would be
interpreted long before InstantDB realised it was dealing with a LIKE
clause.

Is using "\\" causing problems?

Regards

Peter Hearty
Lutris Technologies UK Ltd.
-----Original Message-----
From: Joseph Ferguson <joelemma@yahoo.com>
To: instantdb@enhydra.org <instantdb@enhydra.org>
Date: 07 August 2000 04:23
Subject: InstantDB: string literal escape bugs


>Seems like there is a problem parsing string literals
>with wildcards escaped.
>
>The searchStringEscape looks like '\'
>
>Search strings of '\%' and '\_' both result in unknown
>escape character SQLExceptions. '\\%' and '\\_' seem
>to work.
>
>This isn't a new problem 2.X versions did it too, I
>just never saw it before.
>
>
>__________________________________________________
>Do You Yahoo!?
>Kick off your party with Yahoo! Invites.
>http://invites.yahoo.com/
>---------------------------------------------------------------------------
--
>To unsubscribe from this mailing list, send email to majordomo@enhydra.org
>with the text "unsubscribe instantdb" in the body of the email.
>If you have other questions regarding this mailing list, send email to
>the list admin at owner-instantdb@enhydra.org.
>

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.