Greg Obleshchuk wrote: > > The data types I think are great but can we have a large and small integer? > I noticed some people (embedded systems people) complain about this.
Version 3.0 will use 1, 2, 4, or 8 bytes to store an integer, depending on how big the number is. It uses the fewest number of bytes required. The ROWID will be stored in 1 to 9 bytes - 7 bits per byte - using the fewest number of bytes required.
> Can I suggest that you create a third pre-defined collation (to make it easy > on us that want it) can you create a COLLATE TEXT_CI . Which would be a case > in-sensitive collation.
Why don't *you* write a case-insensitive collating function that is cross-platform and works for UTF-8, UTF-16BE, and UTF-16LE and submit it for inclusion with the library? -- D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
