@Lorne Kates said:
That seemed odd, so I asked instead WHY he neededs a zero row? "It's in the user table. I need a guest account, and I don't want the guest account to show up in the user list".Why not just add another column to the table-- is_guest or something?
Well, then he'd have to change the code everywhere to check "if ! user[is_guest] then..."
Oh. But, how are you going to keep the user from showing up in the list as it is now?
Simple. Just change the code everywhere the user list is used to say "if id > 0 then dowhaever...."
Your solution doesn't make sense here.
If there's only to be one row with a guest then,
a) you still have to have one id with the guest details (and is_guest set to true)b) every other row will have is_guest set to 0
Since you will know the row id of the guest row, whether it be 0, 10 or 251160 there's no point making another column to say the same thing.
Personally I think having 0 for a guest row is perfectly reasonable.
Of course if I misunderstood and there are to be multiple guest rows, then your solution is better.