Comments on: Designing your game’s database

By: saidbakr

saidbakr — Wed, 10 Mar 2010 03:12:40 +0000

Very good meaningful article about database normalization and its benefits.

By: nikolas

nikolas — Mon, 08 Mar 2010 02:05:53 +0000

where do i write all this things!

By: Luke

Luke — Mon, 21 Dec 2009 03:59:35 +0000

The reason that items got done this way(as opposed to user accounts)
isn't really because of OOP at all, so much as flexibility – this
tutorial started out without much of a plan for where it would go, and
I wanted as much flexibility as possible when it came to adding new
items.

By: BUnzaga

BUnzaga — Thu, 17 Dec 2009 08:01:24 +0000

I have just started learning PHP/mySQL in the last couple weeks, and I am trying to follow along with your awesome tutorials. I noticed something, which I am hoping you could help me understand a little better.

I noticed that you are taking an OOP approach to the items, stats, etc, but you didn't do this for user accounts. Is this a standard practice for databases, or was it just something that wasn't really thought about at the time you wrote this tutorial?

As an example, if we followed the OOP approach, we would have two tables for user accounts. One would define what an account was, the other would be the list of accounts.

Could you or anyone else tell me, if this would be a good or bad design architecture? I plan to have one account, with three character slots, which will be tied to the user account. I also plan to have a few other options, such as 'get_news', 'user_address', etc.

Please bare with me and keep in mind the first time I have looked at this stuff was about a week ago when I was lucky enough to find your tutorials.

By: daglees

daglees — Mon, 24 Aug 2009 20:13:16 +0000

This is a very good introduction, it's down to earth and makes sense, thanks!

By: daglees

daglees — Mon, 24 Aug 2009 15:13:16 +0000

This is a very good introduction, it's down to earth and makes sense, thanks!