Today

[rebelliousuno]

Sooo far I have mostly played Dragonshards

Set up the SQL tables for the Gathering

set up the new Gathering Forum....mostly..
time for dinner soon methinks

Comments

[infinidimincorp.livejournal.com]

How are you doing the SQL? I must admit the biggest problem I could see was that the table entries can't be listed in the order in which they are submitted, they need to be listed by some time/date field, which I had no idea how you could set up.

I'd be interested to know your solution, because to be honest I gave up and did it all manually at that stage, and it was horrible.

[rebelliousuno.livejournal.com]

They don't need to be listed in any order at all so long as the primary key of each table is a unique identifier
For example in the login table which stores a users user name and password the primary key is the user name. Sinceno two memberd can have the same user name this is an obvious choice for the primary key. In other cases I have had to add a field to become the primary key (eg the Report table) however this then becomes irrelevant as these can be sorted in other ways. (such as first by gameID then by game week then game day then by the victor for example)

[cyberchi.livejournal.com]

just a sugggestion but not sure if possible as never really played with SQL but would it be possible to add a primary key of an integer number, with each new member being assigned following numbers ie 1,2,3... in order of signups. Sorting by this would in turn sort by timings in essence, tho not I know by date/time stamp... not sure if this is what you are refering to else Im sure its possible to date stamp each SQL database entry...?

[rebelliousuno.livejournal.com]

There is a method to your maddness however there's little point most peoples obsession is to number everything however since the table will be indexed on the primary key which in this case will be the member name which as previously said is unique