Re: [sqlite] Proposal for SQLite and non pure ASCII letters

On Thu, Mar 19, 2009 at 12:31:00PM -0700, Noah Hart scratched on the wall: > Rather my point is that it would be of benefit if SQLite would have > some built in mechanism for a rule-based collation. SQLite *does* have a mechanism for "rule-based" or any-other based collations: User defined

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Nico wrote: >> Number 1, the database is no longer portable. The only solution to >> this is to include the functionality in the core. >Yes but, there is no single Unicode collation. Collation is >language-specific, even when using Unicode. Thus you're asking that >SQLite3 have a plethora of

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

On Thu, Mar 19, 2009 at 09:52:55AM -0700, Noah Hart wrote: > I've been reading and thinking about this topic for a while, and would > like to add my thoughts. > > I realize that we don't "vote" on features, but I feel that this type > of idea has merit. > > It is true, that SQLite has user

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mail.sqlite wrote: > 4. Your comments sound to me that you are living in a 7bit ASCII country, do > you? I am British but currently happen to live in the US, and have lived in every hemisphere whether you cut the earth horizontally or vertically. My

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Igor Tandetnik writes: >This is not quite true. You say custom functions are supported: then you can >do ORDER BY sortkey(textField), >with a suitably defined sortkey() function >(see strxfrm, LCMapString). You can't however build indexes using >such a >function, something you can do with a

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Noah Hart wrote: > Number 2, your platform may not support the sqlite3_create_collation > interface. For example, Firefox now includes SQLite. Unfortunately, > while Firefox supports user defined functions, their implementation > does not support user defined collations. > >

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

I've been reading and thinking about this topic for a while, and would like to add my thoughts. I realize that we don't "vote" on features, but I feel that this type of idea has merit. It is true, that SQLite has user defined collations, and a extension could be registered, but the problem

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

cht- > Von: Roger Binns <rog...@rogerbinns.com> > An: General Discussion of SQLite Database <sqlite-users@sqlite.org> > Datum: 18-03-2009 19:40 > Betreff: Re: [sqlite] Proposal for SQLite and non pure ASCII letters > > -BEGIN PGP SIGNED MESSAGE- &g

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Hello! On Wednesday 18 March 2009 21:51:10 Roger Binns wrote: > > Tcl, Python and other langs have different unicode implementations. The > > realizations are more simple than ICU library but millions of > > applications are using these. I'm will glad to see Tcl/Python/etc. > > unicode

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > Tcl, Python and other langs have different unicode implementations. The > realizations are more simple than ICU library but millions of applications > are > using these. I'm will glad to see Tcl/Python/etc. unicode

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mail.sqlite wrote: > - Please, let us try to bring down the discussion to the intended solution - > a simple way to define and use a "user defined" collating for 8 bit ASCII > characters! You don't need anyone's permission - go ahead and implement

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Hello! > From the German example, you can't even do that (name order is different > than dictionary order). I think we are agreed that the default SQLite > implementation gets ASCII right and makes no attempt to deal > specifically with non-ASCII locales. The ICU extension gets all the >

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

2009 23:55 > Betreff: Re: [sqlite] Proposal for SQLite and non pure ASCII letters > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > I'm know. But you can implement locale-dependent version for single > > language > > only. > > - From the German e

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I'm know. But you can implement locale-dependent version for single language > only. - From the German example, you can't even do that (name order is different than dictionary order). I think we are agreed that the default SQLite implementation

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexey Pechnikov wrote: > You can find locale-independant Unicode extension here: > http://ioannis.mpsounds.net/blog/2007/12/19/sqlite-native-unicode-like- > support/ > > This work fine for me and about 4x faster than ICU. That code should be tidied

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Hello! On Thursday 12 March 2009 10:09:28 Roger Binns wrote: > > I was asking the group their opinion about the usefulness of such > > feature. > > As described I think it is mostly useless.  Sorting even just for West > European languages is not trivial.  For example some countries have a >

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

"Jean-Christophe Deschamps" schrieb im Newsbeitrag news:7.0.1.0.2.20090312013713.0262b...@q-e-d.org... > Perhaps the best way is practice: what's the way to find > this guy named Éric or is it éric, or Eric, or eric? > He lives in MÜNCHEN, München, MUNCHEN, > Munchen or ...

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Jean-Christophe Deschamps wrote: >> You are aware that "standard" SQLite is used in devices with a few >> kilobytes of memory through workstations and servers with gigabytes of it! > > That's precisely why such approach is interesting! I apologise for not making myself clear. Everything that is

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Roger Binns wrote: > Jean-Christophe Deschamps wrote: > >> I'd like to have the group opinion about a feature I would find utterly >> useful in _standard_ SQLite. >> > > You are aware that "standard" SQLite is used in devices with a few > kilobytes of memory through workstations and

[sqlite] Proposal for SQLite and non pure ASCII letters

Roger, >You are aware that "standard" SQLite is used in devices with a few >kilobytes of memory through workstations and servers with gigabytes of it! That's precisely why such approach is interesting! >As far as I can tell you want some extra "standard" collation sequences >and propose

Re: [sqlite] Proposal for SQLite and non pure ASCII letters

Jean-Christophe Deschamps wrote: > I'd like to have the group opinion about a feature I would find utterly > useful in _standard_ SQLite. You are aware that "standard" SQLite is used in devices with a few kilobytes of memory through workstations and servers with gigabytes of it! As far as I can

[sqlite] Proposal for SQLite and non pure ASCII letters

Hello group, I'd like to have the group opinion about a feature I would find utterly useful in _standard_ SQLite. Here's a rewrite of mails sent to hwaci about it, without success so far. Note: I guess that non pure ASCII characters in the sample strings below will translate to '?', but you