i see no point in using 2 db types, why not port all of em to mysql OR berkely, i prefer mysql then
ALso i see no point in making it not compatible with .38 as a whole lot of people still use .38!
*deletes asss*
Cyan~Fire - Tue May 31, 2005 11:51 am
Post subject:
I'm not too worried about bdb, but I do wish it supported .38. Subgame can do it just by saying AllowPreRelease=1, so it can't be that hard, right?
Smong - Tue May 31, 2005 2:24 pm
Post subject:
A problem with mysql scores is what if the db goes down or the connection is temporarily broken. Anyone joining would have reset stats. So a copy of the scores should be kept locally too.
Grelminar has said many times that he's staying with 39pr1, although support for multiple verions would be nice.
Grelminar - Wed Jun 01, 2005 1:23 am
Post subject:
You may not see a point, but that doesn't mean there isn't a point. FWIW, it wouldn't be too hard to port persist to use mysql, but it wouldn't be what you think: stats would be stored in blobs, not as integers, and you'd still have to do a fair bit of work to extract them. Porting the alias db to bdb would be harder, but also possible. I don't see any particularly good reason to spend time on it, though. Porting both to sqlite is probably more likely to happen than either of those options.
I'm not sure how subgame supports both versions at one (securely), so I can't say exactly how hard it would be. If you really really want me to, I'll try to look into it.