That info is actually incorrect. WinFS is still scheduled for Longhorn.
The tech media misinterpreted something.
On Apr 18, 2004, at 8:31 PM, Greg Miller wrote:
Greg Obleshchuk wrote:
I know the MS is looking at replacing the file system with the SQL
engine in Longhorn so they must have
Darren Duncan wrote:
I think the simple answer is that SQLite uses a linked list which can't
know where a page is until reading the next one, but other databases use
something other than a linked list; they would trade a bit of complexity
for speed. -- Darren Duncan
The linked-list structure
Michael Lyubomirskiy wrote:
I got message from the server saying that this group is announcement
only. But I thought I got an email from the moderator saying I can post
by sending to [EMAIL PROTECTED] Could you please tell me how to post
Thank you for your
Bertrand Mansion wrote:
As far as I understand, UTF-8 will read 8859-1 without problem but
ISO-8859-1 will not be able to read UTF-8, unless everything in the UTF8
string uses only 8859-1 codes.
You're wrong, I think.
UTF-8 is a variable length encoding of character codes of the unicode
<[EMAIL PROTECTED]> wrote :
> Bertrand Mansion wrote:
>> As far as I understand, UTF-8 will read 8859-1 without problem but
>> ISO-8859-1 will not be able to read UTF-8, unless everything in the UTF8
>> string uses only 8859-1 codes.
> You're wrong, I think.
> UTF-8 is a variable length
Bertrand Mansion wrote:
I am not sure what this means ?
It is not recommended that you use PHP in a web-server configuration with a
version of the SQLite library compiled with UTF-8 support, since libsqlite
will abort the process if it detects a problem with the UTF-8 encoding.
There is no code
in DLL case of sqlite, do i need to call sqlite_freemem() after
sqlite_exec()/sqlite_get_table(), or only after sqlite_open() , after
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
>> I was wondering if it were possible to straightforwardly
>> programmatically control (hopefully without hacking the engine) which
>> tables will be kept cached in memory by default. For example, if I know
>> that a particular table, or a particular index, will be accessed very
>> frequently, is
I've been away and busy and never had a chance to respond to this.
I decided to continue the response as a sqlite-users thread (as opposed
to just responding directly to andrew) in case others wish to listen-in
i am developing a brand new application (manager) that is 'constrained'
On Mon, 2004-04-19 at 07:04, D. Richard Hipp wrote:
> Darren Duncan wrote:
> > I think the simple answer is that SQLite uses a linked list which can't
> > know where a page is until reading the next one, but other databases use
> > something other than a linked list; they would trade a bit
Mrs. Brisby wrote:
The linked-list structure of overflow storage is part of the problem.
But the fact that SQLite uses synchronous I/O is also a factor. In
order to make BLOBs fast in SQLite, I would have to change to a different
indexing technique for overflow storage *and* come up with some
On Mon, 2004-04-19 at 20:36, D. Richard Hipp wrote:
> Mrs. Brisby wrote:
> >>The linked-list structure of overflow storage is part of the problem.
> >>But the fact that SQLite uses synchronous I/O is also a factor. In
> >>order to make BLOBs fast in SQLite, I would have to change to a
Mail list logo