View Single Post
Old 04-22-2008, 07:44 PM   #1 (permalink)
delayedinsanity
is cute and cuddly
 
delayedinsanity's Avatar
 
Join Date: Mar 2008
Location: Vegas, Baby
Posts: 963
Thanks: 31
delayedinsanity is on a distinguished road
Default Unix timestamp not playing well with others

If I hadn't found this place, I don't know, but I'd probably have the manuals printed out three or four times, with sticky notes everywhere and papers piled on all my animals.

Now, that said, what the hell is going on here?

PHP Code:
public function addNewUser ($szUsername$szPassword$szEmail) {

    
$intTimestamp time();
    
$szVerify substr(md5(rand(10009999) . $intTimestamp), 024); // verification string
 
    
$intUserlevel USER_LEVEL// set default user level

    
$q =  "INSERT INTO " TBL_USERS " (username, password, email, userlevel, registered_on, user_last_active, verify) ";
    
$q .= "VALUES ('$szUsername', '$szPassword', '$szEmail', '$intUserlevel', now(), $intTimestamp, '$szVerify')";

    if (
mysql_query($q$this->connection)) {
        return 
$szVerify;
    } else {
        return 
0;
    }


Looks fine to me, what about you? It works. The problem is it keeps inserting 255 as the timestamp. I even tried to substitute php's time() function with mysql's own native unix_timestamp(), and it still inserted 255.

I can't find any sites that document this happening, so no luck in fixing it so far.

The table column it's going into is an unsigned tinyint(11) which is the same as I've always used for my timestamps.

What the bleep?
-m
delayedinsanity is offline  
Reply With Quote