Personally I'm a big fan of Sqlite (great tool), and I really hope that
this issue can be solved (so we can choose Sqlite).
I understand that solving this issue demands big changes, but I believe
this will take Sqlite to the big players league.
There are great competition in that division
Avner Levy wrote:
We have just finished testing the same scenario with MySql at amazingly
they continued to insert 1500-3000 rows per second even when the
database had 60,000,000 records. I don't know how this magic is done...
Nor do I. If anybody can clue me in, I would appreciate it. I
H, the name of the database IS sql LITE. My guess is that if
it was mean to be the monstrous scalable solution, it would have been
architected this way in the first place.
One thing I find interesting about Sqlite is that I tested in this past week
up to 360,000 records. I had no
With today's hardware power, I think sqlite will easily scale to most
solutions. You may have to purchase a bigger machine, but it is truly easy
and the data file does not corrupt like Access. Access is a piece of trash.
I am helping a company currently with a system that gets 400 million
Allan Edwards wrote:
I have YET to see a database, small to massively scalable that could handle
BLOBS worth anything. ... I prefer the simplicity talk given early. If
someone wants blobs, do it the old fashioned way!
Your concerns are understood, for BLOBs that are truely large. But what
I just finished up the newest version of SQLite Admin for .NET and it is
ready for download for those that are so inclined.
Full Details available here:
http://www.toolfox.com/tf_software/sqliteadmin.aspx
Steven Hodson
ToolFox.com
http://www.toolfox.com
news://news.toolfox.com
I am trying to use SQLite in a commercial application, but I am getting
resistance from the company lawyer:
It is a risk to incorporate SQLite in the [product]. No indemnity
comes with it. We are exposed to third party claims of infringement.
Has anyone else been in this position? Any advice?
Your suggestion was to reconstruct the index from original
table data on a rollback. For a large transaction that touches
most pages of the index, this can give (at best) a 2:1 speedup.
But the other side, the potential slowdown is extreme.
Yeah, there is that drawback. Other DBMSs avoid
This one time, at band camp, D. Richard Hipp [EMAIL PROTECTED] wrote:
My priorities for SQLite are (in order):
1. Reliability and correctness
2. Simplicity
3. Speed
4. Features
Notice that features are at the bottom of the list and that simplicity
and correctness
if you are inside of a transaction, can other people read the database?
or does it lock the database file for the duration of the transaction?
Kind regards
Kevin
--
__
(_ \
_) )
| / / _
[EMAIL PROTECTED] wrote:
DRH: Will the changes to indicies allow us to define arbitrary collation
functions? If so, will those indicies be used when a query is done that
could use the arbitrary collation function?
Likely so. But no promises yet.
--
D. Richard Hipp -- [EMAIL PROTECTED] --
Sorry Richard I meant to send this to the group
Hello,
Last week I raised an issue about case sensitivity in where clauses. In doing a little
research I happened to talk to an Oracle DBA here where I work and asked him the
question of how Oracle handled case sensitivity . He explained it is
12 matches
Mail list logo