questions sqlite and ini

[EK.IceFlake]

Power fault?

I believe that's considered to be your fault for hosting on your local PC. Besides, it's not as if you've never synchronized with the database. Who in their right minds read from database and only save on shutdown? So what? a few nabs lost a few stats from the past minute. Will the world end somehow? No! The problem was you hosting on you grandma's PC. Get a VPS ffs.

But that's not the issue here. The issue is that people don't know how to tackle SQLite and use it properly. So they just claim SQLite sucks and lags. There's a saying here in my country "Cat will say it stinks where she can't reach". And I find that to describe many of you that keep saying SQLite sucks.

You don't understand transactions and how costly they are to insert statements. And the fact that each query will demand a transaction. Regardless of who provides it.

The second and even bigger problem is that SQLite has no caching mechanism. By default, it uses a very safe writing mechanism where it makes sure that every single bit you specified is written to the disk and then it proceeds on you the next query (*cough* transaction *cough*). Read more.

Get real people. INI can't do sh!t when it comes to complex database operations. There's no point in giving you examples because you wouldn't understand sh!t.

How many VPS's do you see with 100% uptime? Exactly.

Also like I said lets say an admin has went through 2000 accounts or so and the server crashed.

[.]

...an admin has went through 2000 accounts or so...

Explain what do you mean by that because it can't be what I think it is. And if it is, that can't be your argument.

[EK.IceFlake]

...an admin has went through 2000 accounts or so...

Explain what do you mean by that because it can't be what I think it is. And if it is, that can't be your argument.

/setaccinfo 1 16 250
/setaccinfo 2 16 250
/setaccinfo 3 16 250
/setaccinfo 4 16 250
/setaccinfo 5 16 250
Anyways in VKs server which might have about 100 database calls or so every minute (when we are reaching our peak player count) we use direct SQLite without any arrays, and it doesn't lag at all. Not even slightly.
p.s. /setaccinfo is a command that sets something about an account in a database, for example /setaccinfo 1 16 250 will set account id 1 column 16 to 250

[jWeb]

But doesn't that mean the information is already in the database and written on disk? So how would a power outage or crash produce any data loss at this point?

[EK.IceFlake]

But doesn't that mean the information is already in the database and written on disk? So how would a power outage or crash produce any data loss at this point?

That's the point, if we save it on disk directly we won't lose it.