[Chdata]

So I want to save a stat related to a player to a database and have these stats cached for each player as well, sort of like clientprefs.

The stats are cached so my plugin natives can return the data instantly instead of having to wait for a SQL callback to read the data.

The stats don't change often or frequently, it might be once a day and if you max out every stat then it's all done for that player, but I want to ensure a scenario doesn't happen where you have to repeat a level up.

Let's say my site goes down (the database goes down), how do I handle making sure the cached stat for this player will eventually be saved?

Using threaded queries of course.


My first thought was to just make a file on the server saying what to send when the database goes back up.

[Potato Uno]

Use both sqlite and mysql at once, and use sqlite as a temporary dump or something if your site goes down?

[Chdata]

Hm.

Since it's more or less an unlocks system (the player unlocks things) that's also for fun, I also have the option of just disabling it if the database is down, which probably will only rarely happen anyway.

[Chdata]

After reading the wiki about SQL:

"Since SQLite is local only, most of the connection parameters can be ignored."

Does this mean for SQLite database functions it simply works as read/write to a file with no possibility of disconnecting?

Should SQLite queries still be threaded to avoid lag, or will non-threaded still work without lag?

[fakuivan]

Originally Posted by Chdata After reading the wiki about SQL: "Since SQLite is local only, most of the connection parameters can be ignored." Does this mean for SQLite database functions it simply works as read/write to a file with no possibility of disconnecting? Should SQLite queries still be threaded to avoid lag, or will non-threaded still work without lag?

They do, If you want to write a lot of stuff on it or just read a non-indexed 60mb+ DB. Why not just using threaded queries, they are not that difficult to implement

[Potato Uno]

SQLite will work forever as it's local. You would need to lose access to the disk srcds is living on to lose connection to SQLite (which, if that happens, you have bigger problems lol).

It's a read/write to a file. You should still use threaded queries even though non-threaded works pretty fast, because if the I/O queue is jammed then the server will lag if it's non-threaded. The I/O time is the lag for sqlite.

[Chdata]

alright. but at least it doesn't die.

Can a single plugin do two db connections at once? I seem to recall that one plugin can only open one connection at a time, but I forgot where I read that.

[fakuivan]

Originally Posted by Potato Uno SQLite will work forever as it's local. You would need to lose access to the disk srcds is living on to lose connection to SQLite (which, if that happens, you have bigger problems lol). It's a read/write to a file. You should still use threaded queries even though non-threaded works pretty fast, because if the I/O queue is jammed then the server will lag if it's non-threaded. The I/O time is the lag for sqlite.

But if the queue is saturated all the time the plugin will crash anyway, as Potato Uno found out the hard way.

[fakuivan]

Originally Posted by Chdata alright. but at least it doesn't die. Can a single plugin do two db connections at once? I seem to recall that one plugin can only open one connection at a time, but I forgot where I read that.

afik yes, you can, write the stats to the sqlite and to the mysql at the same time, then update the mysql when your site goes up again.