I have a mySQL database that receives data from users online once logged in. The data table was created like so...
CREATE TABLE
IF NOT EXISTS `results` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`patient_id` CHAR(10) NOT NULL,
`login_id` CHAR(7) NOT NULL,
`result_date` date NOT NULL,
`result` VARCHAR(4) NOT NULL,
created_at TIMESTAMP NOT NULL,
PRIMARY KEY(`id`)
) DEFAULT CHARSET = utf8 COMMENT = 'List of Member Test Results'
;
Once completed, our IT manager decided to alter my database and PHP code, so he can pull data into his SQL Server database easily. My questions will be two fold, is this necessary and are there potential issues with doing it this way.
The things he changed; altered result_date from a date
to other data type, so he can input on my end in SQL Server format. He altered timestamp/created at so his alteration does not update the timestamp, and he added a boolean/counter column, so his database knows if it has extracted from that row. Also, he added a third date (date like field as non-date type) so when he pulls from my database, he can mark that time.
To me this not only seems like overkill, it also forces me to allow alteration of my database. Lastly, I was scolded for "why would you use created_at timestamp NOT NULL
". Not wanting to call someone out on this, but this issue has me a bit perplexed.