Thanks Olaf.
On Sat, Jan 2, 2010 at 12:49 AM, Olaf Schmidt wrote:
>
> "Artur Reilin" schrieb im
> Newsbeitrag news:op.u5vno6hp1pq...@rear...
>
> > If you are using something like an log system it
> > would be better in this way, but in apps like an
> > shop
"Artur Reilin" schrieb im
Newsbeitrag news:op.u5vno6hp1pq...@rear...
> If you are using something like an log system it
> would be better in this way, but in apps like an
> shop what wouldn't be so great. (thinking about
> ebay with the bets and such..)
Of course, but I
If you are using something like an log system it would be better in this
way, but in apps like an shop what wouldn't be so great. (thinking about
ebay with the bets and such..)
But the idea itself is nice.
Am 02.01.2010, 00:14 Uhr, schrieb Olaf Schmidt :
>
> "Artur Reilin"
"Artur Reilin" schrieb im
Newsbeitrag news:op.u5vlqcps1pq...@rear...
> But that means, if there is a power off or an system crash,
> your data which you send at this moment, goes nirvana.
Yep, as I wrote at the end of my post:
"...in case of an unexpected Close of the App
But that means, if there is a power off or an system crash, your data
which you send at this moment, goes nirvana. But indeed it would be faster
and also would save the hard disc from some writing operations.
Am 01.01.2010, 23:33 Uhr, schrieb Olaf Schmidt :
>
> "Bert Nelsen"
"Bert Nelsen" schrieb
im Newsbeitrag
news:a5ffd531001010911r3de60ec1o44e2c14bce7a7...@mail.gmail.com...
> So SQLite looks at both the database on the disk
> and in memory?
> Wouldn't that be difficult???
Of course... ;-)
And what's so amazing with the SQLite-engine
On Fri, Jan 1, 2010 at 8:11 PM, Bert Nelsen wrote:
> So SQLite looks at both the database on the disk and in memory?
> Wouldn't that be difficult???
>
I don't think that only the memory can be used. Imagine you can have a very
big transaction, 1,000,000 inserts. As
Bert Nelsen wrote:
> So SQLite looks at both the database on the disk and in memory?
> Wouldn't that be difficult???
The in-memory cache is an integral part of the architecture. The whole
transaction model depends on it in large part. For details, see
http://www.sqlite.org/arch.html
So SQLite looks at both the database on the disk and in memory?
Wouldn't that be difficult???
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Bert Nelsen wrote:
> By "corrupted" (the meaning of this word seems to differ depending on the
> user's perspective) you mean that the db is really destroyed and cannot be
> opened anymore?
Yes it's possible, if the power loss occurs at just the wrong moment.
> Another question would be: When I
> Another question would be: When I use transactions, and I said
> ".BeginTrans"
> and insert new records and then, before saying ".CommitTrans", I query the
> records, they seem to be already saved. Can you tell me why this is so?
> Does
> a select command automatically trigger a ".CommitTrans"?
Hello Olaf!
Thanks again for the message.
By "corrupted" (the meaning of this word seems to differ depending on the
user's perspective) you mean that the db is really destroyed and cannot be
opened anymore?
Currently I am working on an application that tracks something like a GPS
signal, and if a
"Bert Nelsen" schrieb
im Newsbeitrag
news:a5ffd530912311004p26a7cc5k1f1bf6f671bef...@mail.gmail.com...
> Your .Sychronous = False property does everything
> as fast as I want, and I am not afraid of losing some
> user data (it's not a critical application) but
> I am
Hello Olaf!
Thank you for your reply. I am using your wrapperlib (and I love it) but I
thought it was a more general question and had nothing directly to do with
your wrapperlib. But I am not sure anymore what is yours and what is common
Sqlite.
Your .Sychronous = False property does everything as
On Thu, Dec 31, 2009 at 9:06 AM, Bert Nelsen wrote:
> It's here:
>
> https://developer.mozilla.org/en/Storage:Performance
>
Thanks. I've removed the outdated information.
Cheers,
Shawn
___
sqlite-users mailing list
"Bert Nelsen" schrieb
im Newsbeitrag
news:a5ffd530912310853t7024d908tefbf1ef40df47...@mail.gmail.com...
> I would like to make writes to my SQLite db faster.
In what regard (under which circumstances) is it slow
currently?
What's your typical recordcount per
It's here:
https://developer.mozilla.org/en/Storage:Performance
On Thu, Dec 31, 2009 at 6:04 PM, Shawn Wilsher wrote:
> Where did you see this? It's inaccurate, and if I can, I'll remove it. If
> you want to use a proper asynchronous statement execution which wraps your
Where did you see this? It's inaccurate, and if I can, I'll remove it. If
you want to use a proper asynchronous statement execution which wraps your
statement[s] in a transaction, you want to use this:
https://developer.mozilla.org/En/Storage#Asynchronously
Cheers,
Shawn Wilsher
Mozilla
Hello,
I would like to make writes to my SQLite db faster.
I was thinking about the Async method, but I think I remember reading
somewhere that it may cause database corruption.
Now I read something on the Mozilla pages, and I don't understand what
exactely they are doing.
Do they bundle
19 matches
Mail list logo