Re: Re: [sqlite] A proposal for SQLite version 3.0

2004-04-09 Thread Nuno Lucas
=== On 2004-04-09, D. Richard Hipp wrote === .. > >The reason for not doing this is that maintenance of the counter >slows down inserts and deletes. Is having a constant-time count(*) >really work slower inserts and deletes? If you have opinions on >this, speak up now, because it won't be an

[sqlite] Norton AntiVirus conflict on Mac

2004-04-09 Thread James W. Walker
Maybe I'm the only one still using the classic Mac code path in SQLite, but for the record I'll describe a problem I had with Norton AntiVirus. It was causing sqliteOsDelete to fail with a file-busy error, presumably because NAV was checking the file for viruses, and then a subsequent attempt

Re: [sqlite] A proposal for SQLite version 3.0

2004-04-09 Thread Andrew Carter
Windows UTF-16 is represented by WCHAR. It is always 2 bytes. UCS-2 can be 3 or more bytes but these are for extended characters outside the ones used for real language. For example, musical notation symbols use the third byte. I don't think any OS's use UCS2 directly. I know Oracle supports

Re: [sqlite] A proposal for SQLite version 3.0

2004-04-09 Thread Andrew Carter
I'm assuming UTF-8 support will still be there as well? For Windows applications, UTF-16 is much more prevalent. -- Andrew On Wed, 7 Apr 2004, Christian Smith wrote: > On Wed, 7 Apr 2004, D. Richard Hipp wrote: > > >A design proposal for SQLite version 3.0 can be found at: > > > >