Support Call: 116
Subject RgF UG Cadet problem #4
Status Closed
Assigned To RA Snappleguy
Logged By GEN Javin "Entropy" Ke'ylle
Logged On Oct 11, 2003
Call Text I've just been going over the problems that Phil has found and reported and noted something that could possibly have some bearing on the matters. The last 6 recruits that were supposed to make it to the RgF UG all had the exact same PIN, 1298. It's been a few years since I've worked on database stuff, and I'm not exactly clear on how the test is supposed to work, but this was my thought. If the PIN generation is somehow screwed up and it's trying to add people with the same PIN, and assuming PIN is the primary key, the DB probably isn't going to like the attempt to add another record with an already used PIN (primary key).
Action History
Oct 12, 2003 Hmmm....a database will NOT ever store the same key twice. You can't even manually modify it to do that. Something else has to be going on, I'll look into it.

Action updated by BGN Snappleguy.
Oct 15, 2003 An SQL statement in the entry test processing page was inserting
the cadets into the wrong table (Table "Cadet" instead of "Cadets").
Hence why no cadets were being added.

There still has to be a lot of testing done though, as there's a lot
that goes on in the joining process. This should at least fix SOMETHING
though. :)

Action updated by BGN Snappleguy.
Oct 17, 2003 It works. I just added a test character as 1299 via the join forms and passing the test.

Next cadet should be 1300.

My God was that one a pain in the @$$

Action updated by BGN Snappleguy.