SQLite3?

[kskels]

Maybe there can be one tankage world per server.. So that every server can have it's own database with it's own SQLite database? So that servers are not aware and there can be as much servers as needed or so :D

If one tankage world could be reasonable limited size the DB file should not grow too big, hopefully? Just got excited to try SQLite someday :D

[peteb]

I'm a bit skeptical though, maybe for user accounts and stuff like
that? I don't think the world would work well in a DB like that; it's
just a lot of binary data.

-- Peter

On Jun 4, 2011, at 1:00 PM, kskels
[email protected]
wrote:

Maybe there can be one tankage world per server.. So that every server can have it's own database with it's own SQLite database? So that servers are not aware and there can be as much servers as needed or so :D

If one tankage world could be reasonable limited size the DB file should not grow too big, hopefully? Just got excited to try SQLite someday :D

Reply to this email directly or view it on GitHub:
#63

[peteb]

But I like the idea with one world per server :) makes the
implementation easier!

-- Peter

On Jun 4, 2011, at 1:00 PM, kskels
[email protected]
wrote:

Maybe there can be one tankage world per server.. So that every server can have it's own database with it's own SQLite database? So that servers are not aware and there can be as much servers as needed or so :D

If one tankage world could be reasonable limited size the DB file should not grow too big, hopefully? Just got excited to try SQLite someday :D

Reply to this email directly or view it on GitHub:
#63

[kskels]

Well, if the DB file is local, that should be fast, besides, can there be many people due to very high real-time network needs?

[peteb]

Well, we should strive for supporting as many players as possible, we
should avoid adding bottlenecks :) But I wasn't thinking of DB
performance, really, just that DBs like that aren't meant for binary
data. I've also heard sqlite shouldn't be used on server-side due to
performance. I don't see a use case where sqlite would be better on
the server, compared to for example postgres. It's mainly used for
user settings in clients.

-- Peter

On Jun 4, 2011, at 1:51 PM, kskels
[email protected]
wrote:

Well, if the DB file is local, that should be fast, besides, can there be many people due to very high real-time network needs?

Reply to this email directly or view it on GitHub:
#63 (comment)