WTF MYSQL!!

Added "NULL" option to all appropriate TIMESTAMP columns so that they behave how we expect them to.
pull/263/head
Justin Richer 2012-11-15 15:23:54 -05:00
parent f9aafb5edd
commit 150c4032fd
1 changed files with 5 additions and 5 deletions

View File

@ -1,7 +1,7 @@
CREATE TABLE access_token ( CREATE TABLE access_token (
id BIGINT AUTO_INCREMENT PRIMARY KEY, id BIGINT AUTO_INCREMENT PRIMARY KEY,
token_value VARCHAR(4096), token_value VARCHAR(4096),
expiration TIMESTAMP, expiration TIMESTAMP NULL,
token_type VARCHAR(256), token_type VARCHAR(256),
refresh_token_id BIGINT, refresh_token_id BIGINT,
client_id VARCHAR(256), client_id VARCHAR(256),
@ -23,9 +23,9 @@ CREATE TABLE approved_site (
id BIGINT AUTO_INCREMENT PRIMARY KEY, id BIGINT AUTO_INCREMENT PRIMARY KEY,
user_id VARCHAR(4096), user_id VARCHAR(4096),
client_id VARCHAR(4096), client_id VARCHAR(4096),
creation_date TIMESTAMP, creation_date TIMESTAMP NULL,
access_date TIMESTAMP, access_date TIMESTAMP NULL,
timeout_date TIMESTAMP, timeout_date TIMESTAMP NULL,
whitelisted_site_id VARCHAR(256) whitelisted_site_id VARCHAR(256)
); );
@ -127,7 +127,7 @@ CREATE TABLE redirect_uri (
CREATE TABLE refresh_token ( CREATE TABLE refresh_token (
id BIGINT AUTO_INCREMENT PRIMARY KEY, id BIGINT AUTO_INCREMENT PRIMARY KEY,
token_value VARCHAR(4096), token_value VARCHAR(4096),
expiration TIMESTAMP, expiration TIMESTAMP NULL,
auth_holder_id BIGINT, auth_holder_id BIGINT,
client_id VARCHAR(256) client_id VARCHAR(256)
); );