Re: [sqlite] SQLite 3.0 - Why only one text encoding per database?

2004-06-21 Thread Darren Duncan
At 5:23 PM -0500 6/21/04, Tim wrote: It sounds like SQLite 3.0 only supports one text representation per database ("Internally and in the disk file, the same text representation is used everywhere."). Is there a particular reason for this limitation? What if I want to store one column as UTF8

Re: [sqlite] SQLite 3.0 - Why only one text encoding per database?

2004-06-21 Thread D. Richard Hipp
Tim wrote: > It sounds like SQLite 3.0 only supports one text representation per database > ("Internally and in the disk file, the same text representation is used > everywhere."). Is there a particular reason for this limitation? The reason is to keep the API simple. If the programmer selects a

[sqlite] SQLite 3.0 - Why only one text encoding per database?

2004-06-21 Thread Tim
It sounds like SQLite 3.0 only supports one text representation per database ("Internally and in the disk file, the same text representation is used everywhere."). Is there a particular reason for this limitation? What if I want to store one column as UTF8 text and another column as UTF16? Ot