=== On 2003-11-21, Clark, Chris wrote ===
..
>Check out http://sqlite-wince.sourceforge.net/ its not been updated in a while so its
>the 2.80 version.
>
>Good luck,
>
>Chris
Just a small correction, the sqlite-wince release uses the last stable sqlite version
(version 2.8.6).
What needs to be do
Hello,
I've ported SQLite to a system where it is important for speed that when
writing memory to a file that the memory blocks be aligned to 128 or
even 256 bytes and that the size of the blocks be as large as possible,
preferably a power of two. After looking through the code it seems like
Hello,
I read your paper and it was interesting. I am an advocate for improving
the speed of SQLite where ever possible and after reading your paper and
applying the experiences of using MS SQL server these are my thoughts.
1. All transactions should be Read Only (no locking) with an option to t
Come on fellas! Why not just setup a forum on the sqlite.org website or
something, and kill this whole list server thing. Maybe Linux is just too
complex for some people to handle list servers with! : - )
Thanks,
Allan
-Original Message-
From: Bernie Cosell [mailto:[EMAIL PROTECTED]
S
On 22 Nov 2003 at 22:23, Bert Verhees wrote:
> > It seems to me that all the people send theiur ewmail double, and that it
> > is a failure in the list software configuration.
> >
> > This email has only one TO: sqlite-users <[EMAIL PROTECTED]>
> > And no CC or BCC, thus, if this is posted twice,
> It seems to me that all the people send theiur ewmail double, and that it
> is a failure in the list software configuration.
>
> This email has only one TO: sqlite-users <[EMAIL PROTECTED]>
> And no CC or BCC, thus, if this is posted twice, it is the list software
Ever thought that it might be s
> It seems to me that all the people send theiur ewmail double, and that it
> is a failure in the list software configuration.
>
> This email has only one TO: sqlite-users <[EMAIL PROTECTED]>
> And no CC or BCC, thus, if this is posted twice, it is the list software
>
> kind regards
> Bert Verhees
It seems to me that all the people send theiur ewmail double, and that it
is a failure in the list software configuration.
This email has only one TO: sqlite-users <[EMAIL PROTECTED]>
And no CC or BCC, thus, if this is posted twice, it is the list software
kind regards
Bert Verhees
-
Hi, I've got few questions:
1/ I've got sqlite like PHP module (under windows). I tried this:
a)execute script 1 (selecting from some table), it tooks 2 minutes
b)execute script 2 , it tooks 3 minutes
c)execute them both at the same time (from different browser windows), bo
D. Richard Hipp wrote:
Feedback is requested on the paper found at:
Richard,
SQLite is one of my favorite examples of good open-source s/w.
I read (with great interest) your paper, and would not have a problem
with any of the proposals being implemented. All would have some benefits.
However, a
My uses of SQLite are multithreaded (mostly) single process. So, an
approach that would appeal to me is "client-server" where the server
is a thread in my process, and the clients are other threads. Adding
a lock manager to the server thread would permit fine grained locking
with ACID properties.
Mrs. Brisby wrote:
Instead of keeping an "undo" journal- consider using a "changes"
journal-- each writer could use it's own journal then only at commit
would each worker actually start making changes to the database.
> ...
>
Note that these changes will contain not only the values they are
storing
hi:
thank for any reply!
I'm using tomcat4 and post html form data with utf-8 encoding.
I has set the jvm argument like : -DSQLite.encoding=utf-8, but i can't
insert the utf-8 string to the table.
I do some test and I found that I must transform string to iso8859-1
firstl
This is more rambling than anything else. I hope I'm reasonably coherent
before coffee...
Instead of keeping an "undo" journal- consider using a "changes"
journal-- each writer could use it's own journal then only at commit
would each worker actually start making changes to the database.
DEFER_W
> Feedback is requested on the paper found at:
>
> http://www.sqlite.org/concurrency.html
>
> Your analysis and ideas will help to make SQLite a
> better database engine. Thanks.
In my somehwhat limited knowledge of database design, I'd advocate all the
options in section 4 (ie transaction o
Feedback is requested on the paper found at:
http://www.sqlite.org/concurrency.html
Your analysis and ideas will help to make SQLite a
better database engine. Thanks.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
16 matches
Mail list logo