"Daniel White" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> Oh well, there are one or two 'hacks' around it. The first is
> to use COLLATE BINARY, or COLLATE NOCASE after the SQL query.
> This appears okay on the surface, but probably ignores
> unicode chars or something. It may
Cheers both of you, it seems this problem is indeed
linked with the "no such collation sequence: iunicode"
error as Dan mentioned.
After some research, I found out that the root of
the problem is unsurmountable at present. I quote from:
http://www.mediamonkey.com/forum/viewtopic.php?p=84197
Hi All,
Looks like there is some interest. I will announce when I release it.
Currently I am developing an interactive user shell client. This shell is
used for my client/server development. It can also be embedded for any
clients user interface.
The request/response is a little slow for some
I am using SQLite for a storage backend for a phone application, the
application downloads the information from an XML-RPC based host and
sends information to and from a database. The data is held in the
database so the phone application doesn't have to get all the
information every 15
While upgrading from an older SQLite 3.4.2, I stuble upon the
following build problem.
me\sqlite3\btree.c:61: error: expected ';', ',' or ')' before '-' token
mingw32-make: *** [obj-i386\me\sqlite3\btree_sqlite3.o] Error 1
btw. I read the upgrade guide: http://sqlite.org/34to35.html
...
On Jun 14, 2008, at 9:08 PM, Daniel White wrote:
> The course of action I thought you implied was to change
> it from "hexion" to "Hexion", and so I hoped that would
> return the results, but it still doesn't.
>
> "Still" meaning, just like the small 'h', 'H' doesn't
> work either.
>
The answer
> Which way is it stored in the database? Show the output of this
> statement:
>
> SELECT SongTitle FROM songs WHERE SongTitle like 'hexion';
There are 8 records of Hexion in the database, so after a printout
to the console with a carriage return after each value, I basically get:
Hexion
Hexion
"Daniel White" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> The course of action I thought you implied was to change
> it from "hexion" to "Hexion", and so I hoped that would
> return the results, but it still doesn't.
Which way is it stored in the database? Show the output of
The course of action I thought you implied was to change
it from "hexion" to "Hexion", and so I hoped that would
return the results, but it still doesn't.
"Still" meaning, just like the small 'h', 'H' doesn't
work either.
Dan also mentioned the capital letter thing so it
was a reply to him as
"Daniel White" <[EMAIL PROTECTED]>
wrote in message news:[EMAIL PROTECTED]
> Funny you should mention the capital at the start
> to make "Hexion". I thought of that just after I
> posted. But it doesn't solve the problem unfortunately.
> Zero results are still returned.
What do you mean, "still"
Thanks Dan and Igor for clarifying the 5th param.
I'm guessing it's safe to leave it at 0 if I
just use one SQL statement then.
Funny you should mention the capital at the start
to make "Hexion". I thought of that just after I
posted. But it doesn't solve the problem unfortunately.
Zero results
Gerry Snyder wrote:
> Harold Wood wrote:
>> I have several tables that i need to datestamp as transactions occur and
>> then retrive with a select where between X and Y.
>>
>> What is the best way to do this in SQLite?
>>
> Look at
>
>
12 matches
Mail list logo
