The server is now able to interface with an SQLite database. It took me a little bit of fiddling around to get the interface wrapper just the way I want it to work. Now that it is done, i'm very happy with it. Following this completion, I have started the players table, which will maintain persistent storage of player accounts. As it follows, I will be working on the new account/login routines shortly.
Even though I was shooting for at least 1 new screenshot a week, I don't think it is worth it at this point in time. I'm at the point right now, were coding takes precedence over modelling and terrain building. So rather than show a screenie of the same old stuff, I figured I'd hold off until a few important features are built into the game. That said, I have been taking care of some important components of the server.
The server is now able to interface with an SQLite database. It took me a little bit of fiddling around to get the interface wrapper just the way I want it to work. Now that it is done, i'm very happy with it. Following this completion, I have started the players table, which will maintain persistent storage of player accounts. As it follows, I will be working on the new account/login routines shortly.
The server is now able to interface with an SQLite database. It took me a little bit of fiddling around to get the interface wrapper just the way I want it to work. Now that it is done, i'm very happy with it. Following this completion, I have started the players table, which will maintain persistent storage of player accounts. As it follows, I will be working on the new account/login routines shortly.
Previous Entry
Network Subsystem v1.0
Next Entry
Progress Report
Comments
April 14, 2006 11:10 AM
I'm a db newbie too. I decided to kick my flatfile habits and give databases a shot. I chose SQLite for the main reason that it is an embedded database, so you don't need to use a loopback socket connection to connect to the db. I'm just starting out, but if you change your mind on the flatfile stuff, i'd recommend giving SQLite a shot. I've been happy with it thus far.
April 14, 2006 11:56 AM
There's nothing to stop you using a flat file database and something a bit more fully featured.
I threw together a simple MUD that ran off a flat file DB. I had files for the various tables i.e. room, exit, player, object, permissions etc but I wrote an interface to the flat file commands. So whenever I needed data I used that interface.
pseudocode
x = DbGet(Tablename, Key, Value etc)
Then if you want to hook it up to some SQL DB instead you simply rewrite the DbGet routine to fire off sql instead of delve in to a flat file.
Of course with some OO this can be really sweet with plugable components.
I threw together a simple MUD that ran off a flat file DB. I had files for the various tables i.e. room, exit, player, object, permissions etc but I wrote an interface to the flat file commands. So whenever I needed data I used that interface.
pseudocode
x = DbGet(Tablename, Key, Value etc)
Then if you want to hook it up to some SQL DB instead you simply rewrite the DbGet routine to fire off sql instead of delve in to a flat file.
Of course with some OO this can be really sweet with plugable components.
April 20, 2006 10:02 AM
Advertisement
Latest Entries
Interfacing C++ and Python (Part 2)
4966 views
Interfacing C++ and Python (Part 1)
2902 views
Standalone SVN Repository
2167 views
Crash Recovery
1400 views
Progress Report
1306 views
More stuff
1523 views
Network Subsystem v1.0
1441 views
Animation Channels and Polygon Offset
1859 views
Model Manager changes
1400 views
Advertisement
And don't worry about the lack of a screenshot -- I think nearly every developer hear knows exactly what you mean when you say that code > graphics during development. [smile]