Re: ENUM() vs TINYINT

On 9/21/2015 9:03 AM, Richard Reina wrote: I have a column name quarter which I need to have 5 possible inputs; 1, 2, 3, 4, or OT. Because of the OT possibility I am leaning towards ENUM. Hence, I am also thus considering ENUM('first', 'second', 'third', 'fourth', 'overtime') as the input will

Re: ENUM() vs TINYINT

> From: Richard Reina > > I have a column name quarter which I need to have 5 possible inputs; 1, 2, > 3, 4, or OT. Because of the OT possibility I am leaning towards ENUM. > Hence, I am also thus considering ENUM('first', 'second', 'third', > 'fourth', 'overtime') as the

ENUM() vs TINYINT

I have a column name quarter which I need to have 5 possible inputs; 1, 2, 3, 4, or OT. Because of the OT possibility I am leaning towards ENUM. Hence, I am also thus considering ENUM('first', 'second', 'third', 'fourth', 'overtime') as the input will primarily be used in written descriptions. Is

Re: ENUM() vs TINYINT

I'm sure your enum is a fine option, but 0,1,2,3,4 would do the same thing. And you could add a comment to the table to describe it if desired. On Mon, Sep 21, 2015 at 8:03 AM, Richard Reina wrote: > I have a column name quarter which I need to have 5 possible inputs; 1,

Re: ENUM vs TINYINT

Cemal, I recall hearing a similar question mentioned in a previous email thread. In fact, here it is:

Re: ENUM vs TINYINT

AM Subject: Re: ENUM vs TINYINT Cemal, I recall hearing a similar question mentioned in a previous email thread. In fact, here it is: http://groups.google.com/groups?hl=enlr=ie=UTF-8threadm=c6h60e%2419dd%241%40FreeBSD.csie.NCTU.edu.twrnum=1prev=/groups%3Fq%3D%2522enum%2Bor%2Btinyint%2522%26hl

ENUM vs TINYINT

Hi all, I need a boolean column and at to this time I always used ENUM('Y','N') for this. I'am wondering that will there be a performance difference between using ENUM('Y','N') and TINYINT(1) or BOOLEAN?. And put 0 or 1 to TINYINT column. Best Regards, Cemal Dalar a.k.a Jimmy System

Optimization question - enum vs tinyint

Hi, I currently store some boolean values in tinyint(1) unigned fields. When running the procedure analyze on my tables, I am told that the best data type for these fields would be an enum(0,1). Is that true? How is that faster than tinyints? Also, does specifying the length of an