I'm not sure this will fix your problem, but I'd recommend just doing this instead of using a flag:
PHP Code:
INSERT OR REPLACE INTO tPlayer (account, subscription, lastlogin, gelats, communityname) VALUES ('pc:5306287', 'trial', 1311299072, 0, 'guest')
If inserting the row would cause a constraint conflict, it deletes the existing row causing the conflict and inserts the row. If there is no conflict, it just inserts the row.
It should get rid of any issues resulting from out-of-sync database/player attributes (e.g. if a player is reset or rolled back).
Note that this
will change the rowid for the player's entry, but you should never rely on the rowid. If you specify a PRIMARY KEY column, it probably won't change the rowid.