Re: Design help for Scheduling db.
Posted by: Rick James
Date: February 13, 2010 01:12AM

Looks like all the fields are NULLable -- shouldn't they be NOT NULL?

[Open,AM,PM,Close,Any,None] -- Isn't "Any" really "Y" on all of the first 4? And None is "N" on all. (4 bits works better).

I would use bitstrings for most of these things -- but if you are not comfortable with boolean arithmetic, don't tackle it. A week's worth of time slots could be represented as 28 (7*4) bits (INT UNSIGNED).

int(3) is not what you might think -- see TINYINT UNSIGNED or SMALLINT UNSIGNED.

"not good coding practice since they are not portable and are native to mySQL" -- If you do change to another database vendor, you will find there to be a lot of changes anyway. Portability --> straight jacket.

Options: ReplyQuote


Subject
Written By
Posted
February 11, 2010 12:27PM
Re: Design help for Scheduling db.
February 13, 2010 01:12AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.