;
> This was tested on 3.2.1
>
> - Original Message -
> From: "Brandon, Nicholas" <[EMAIL PROTECTED]>
> To:
> Sent: Monday, December 05, 2005 12:15 PM
> Subject: RE: [sqlite] Regarding String Comparision
>
>
> >
> > Rob/Ritesh
>
field like 'value' it isn't. If you don't use '%value%' it
will do an exact match (it seems).
This was tested on 3.2.1
- Original Message -
From: "Brandon, Nicholas" <[EMAIL PROTECTED]>
To:
Sent: Monday, December 05, 2005 12:15 PM
Subject: RE:
Rob/Ritesh
>Also keep in mind that such a search is CASE SENSITIVE.
>There are two solutions to that, either makes the collation
>case insensitive or do a:
I don't have access to SQLite immediately but I seem to remember in one of
my applications that the use of
select * from test where filenam
ng either the insert or the select
- Original Message -
From: "Martin Engelschalk" <[EMAIL PROTECTED]>
To:
Sent: Monday, December 05, 2005 10:06 AM
Subject: Re: [sqlite] Regarding String Comparision
Hi,
I am not sure if i understand your question right. Perhaps the follow
Thanks Martin
Thats exactly what I wanted to know. And I think this is the fastest
reply/solution I ever got!!
ritesh
On Mon, 2005-12-05 at 14:36, Martin Engelschalk wrote:
> Hi,
>
> I am not sure if i understand your question right. Perhaps the following
> will help:
>
> The behaviour dep
Hi,
I am not sure if i understand your question right. Perhaps the following
will help:
The behaviour depends on the comparison operator.
If you do
select ...
from FileTable
where FileName = "testfile.txt"
then the whole string will be matched
If you do
select ...
from FileTable
where Fil
6 matches
Mail list logo
