Aaron
I don't think you're doing anything wrong. % should match zero or more characters, so I
think it ought to match an empty string. I can't promise when you'll see a fix for this
though. Is it likely to cause you major problems?
Pete
----- Original Message -----
From: <arh14@cornell.edu>
To: <instantdb@enhydra.org>
Sent: Wednesday, February 21, 2001 8:36 PM
Subject: InstantDB: Zero-length strings
>
> It seems that zero-length strings in an insert statement result in nulls
> in the database. Either that or the % wildcard is not working. My
> problem is that when I insert some non-null zero-length string values
> into some columns
>
> e.g. INSERT INTO Foo VALUES ('','','')
>
> an immediate search with wildcards fails
>
> e.g. SELECT * FROM FOO WHERE Col1 LIKE '%%' AND Col2 LIKE '%%' AND Col3 LIKE '%%'
>
> To my understanding % should collaps to "any non-null string value", so
> %% should be matching the zero-length string values. The second I change
> the insert statement to insert strings consisting of a single space
> character, the select statement works.
>
> Am I doing something wrong here?
>
> Aaron Hamid
> -----------------------------------------------------------------------------
> 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.
|