Not that you haven't had the debate before, but I hope this discussion
of my enhancement request for a raw flip() or reverse() function helps
to highlight some basic issues relating to Unicode in the database; I
don't mean to be beating any dead horses.
Roger Binns wrote:
quoteMy point was
Roger,
I have had a very brief time observing the SQLite community, the
opposite of your own experience, but I have been working with a variety
of databases since 1985: PICK, Revelation, FoxPro, Paradox, MS-Access,
Oracle, and SQLServer, among others. I'm not a newbie to databases but
am a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
The requirements for the flip() function I've requested are unambiguous:
simply reverse the string, raw codepoint by codepoint.
My point was that your requirements are that, yet someone else wanting a
flip function could want
Yet I don't want to do this reversal in my application. I am not a C
programmer and would have to rely upon data-providers to talk to the
database. Providers, as good as they may be, are not 100% transparent
conduits between the client app and the database. Right now, three of
them are
Roger wrote:
quote... You still have the issue that the [flip()] code would likely be
excluded by default just as
soundex is, so it would still require re-compiling SQLite. /quote
I would hope that it could be included by default. Those who are
concerned about the overall weight of the EXE
Roger,
Also, you mentioned that it could take some time for a flip() function
to make its way into the OSX version assuming it had been accepted and
put on the docket.
I can wait a good long time for SQlite to add a flip() function. About
eight years ago now I wrote my app, a full-text search
On 11/19/09 14:55 , Tim Romano tim.rom...@yahoo.com wrote:
The app was written in .NET against MS-Access; my Macintosh colleagues
couldn't use it. They outnumbered the Windows users. But I didn't own a
Mac and had never programmed on a Mac. But now Adobe Flex/AIR with
SQLite is available,
Thanks for the heads-up, Jean-Denis.
I was going to try to deploy the almost-finished Flex/AIR app on my
wife's Mac notebook this weekend to see how it goes. That it works
quickly under Windows XP is all I know at this point. I am very
concerned about query performance and app
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
I would hope that it could be included by default.
[Note I do not speak on behalf of the SQLite team but have been an observer
for many years]
Your request is extremely unlikely to go into the SQLite core as the bar is
*very*
I wanted to get a clearer sense of how SQLite treats decomposed Unicode
characters (http://unicode.org/faq/char_combmark.html#2) in its various
string functions and with the concatenation operator yet there doesn't
seem to be any way to get them into the database using the SQlite3.EXE
Tim Romano tim.rom...@yahoo.com wrote:
I wanted to get a clearer sense of how SQLite treats decomposed
Unicode characters (http://unicode.org/faq/char_combmark.html#2) in
its various string functions and with the concatenation operator yet
there doesn't
seem to be any way to get them into
Hi Igor,
The blob (x'41' is a blob literal) is expected to contain a UTF-8
sequence, I believe.
That means the user enters the hex UTF-8 (or 16 depending on base
encoding) representation of the character. E.g.:
select cast(x'c389' as text);
É
Something like:
select chrw(x'c9');
The blob (x'41' is a blob literal) is expected to contain a UTF-8 sequence, I
believe.
I think it should be a database encoding which is either UTF-8 or
UTF-16. So for Tim's case if his database encoding is UTF-16 insert
statement can be like this:
insert test (id, myTextColumn) values(1,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
This would be a convenient function to have. Are there technical
issues/obstacles?
In general for all these feature requests for more functions there is no
need for them to be added to the SQLite core. There is a very simple API
On 18 Nov 2009, at 6:05pm, Roger Binns wrote:
Tim Romano wrote:
This would be a convenient function to have. Are there technical
issues/obstacles?
In general for all these feature requests for more functions there is no
need for them to be added to the SQLite core. There is a very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Slavin wrote:
I googled, and there doesn't seem to be a page which describes the abilities
and limitations the extension system has.
A C function of your choosing can be called on each new connection being
created:
I respectfully disagree, Roger, about the simplicity. Creating an
external DLL would complicate my distribution scenario significantly
because I'll have just as many users of my little database application
working with Apple OSX as with Windows. I guarantee you, it would be
easier for the
Apologies. An accident -- I was trying to grab the To: address from a
previous email and didn't realize there was a big thing attached. I
don't see anything attached to this one. I hope there isn't.
Tim Romano
Jean-Christophe Deschamps wrote:
Please don't set the ReplyTo field to the list
Tim Romano tim.rom...@yahoo.com wrote:
I respectfully disagree, Roger, about the simplicity. Creating an
external DLL would complicate my distribution scenario significantly
because I'll have just as many users of my little database
application working with Apple OSX as with Windows.
You
On 18 Nov 2009, at 9:27pm, Roger Binns wrote:
A C function of your choosing can be called on each new connection being
created:[snip]
Thanks for your detailed answer.
Simon.
___
sqlite-users mailing list
sqlite-users@sqlite.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Romano wrote:
I respectfully disagree, Roger, about the simplicity. Creating an
external DLL would complicate my distribution scenario significantly
because I'll have just as many users of my little database application
working with Apple
21 matches
Mail list logo
