2013/05/22 21:17 +, Rick James
In query syntax, TRUE is the same as 1; FALSE is the same as 0.
and UNKNOWN is NULL. (I actually have used a three-state comparison.)
It has been suggested that one who wants a real two-state field use the type
CHAR(0) NULL.
If you ha
On 05/22/2013 06:55 PM, Neil Tompkins wrote:
Hi,
I've just created some tables that I designed using the MySQL Workbench
Model. However, the database type BOOLEAN which was in my models has been
converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on
Windows 2008 server.
BOO
In query syntax, TRUE is the same as 1; FALSE is the same as 0.
A minor syntax note: ENUM('FALSE', 'TRUE') would require quotes when using it.
If you have multiple 'flags', consider the SET datatype. (Yeah, it is somewhat
clumsy.)
If you have installed 5.6, simply try BOOL or BOOLEAN. I susp
Why not use ENUM with True|False or Y|N Only issue is it doesn't throw
and error of you enter an illegal value but I don't think I've ever
flagged the field as NOT NULL.
On Wed, May 22, 2013 11:32, Darryle Steplight wrote:
> Hey Neil,
> Why not just store it as a TINYINT, that's what I do when I
Hello Neil,
On 5/22/2013 1:05 PM, Neil Tompkins wrote:
Hi, Like the link states
"For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data
entry. For instance, it's still possible to insert a value of "2" (any
integer up to the TINYINT max value). I personally don't see the added
Hi Shawn
I plan in installing the latest MySQL version tomorrow. Does MySQL not
support Bool eg true and false
Neil
On 22 May 2013, at 19:05, shawn green wrote:
> Hello Neil,
>
> On 5/22/2013 1:05 PM, Neil Tompkins wrote:
>> Hi, Like the link states
>>
>> "For clarity: a TINYINT(1) dataty
Hey Neil,
Why not just store it as a TINYINT, that's what I do when I only care
about 0 or 1 values?
On Wed, May 22, 2013 at 2:19 PM, Neil Tompkins wrote:
> Hi Shawn
>
> I plan in installing the latest MySQL version tomorrow. Does MySQL not
> support Bool eg true and false
>
> Neil
>
> On 22
ext does less well with simultaneous IOPs than xfs.
> -Original Message-
> From: Manuel Arostegui [mailto:man...@tuenti.com]
> Sent: Wednesday, May 22, 2013 12:22 AM
> To: Rafał Radecki
> Cc: mysql@lists.mysql.com
> Subject: Re: Mysql server - which filesystem to choose? Is it really
> tha
Hi, Like the link states
"For clarity: a TINYINT(1) datatype does NOT ENFORCE a boolean value data
entry. For instance, it's still possible to insert a value of "2" (any
integer up to the TINYINT max value). I personally don't see the added
value of a 'BOOLEAN' synonym type which infact behaves un
Hi,
I've just created some tables that I designed using the MySQL Workbench
Model. However, the database type BOOLEAN which was in my models has been
converted to TINYINT(1); I'm currently running MySQL Version 5.6.2-m5 on
Windows 2008 server.
Any ideas why this has been removed ?
Neil
Rafal,
I benchmark a lot on various hardware and software configurations. When I
started 2 years back I went along with the general consensus that XFS is
faster than ext4 for MySQL. I recently had the opportunity to see how much
of a difference, if any, it made. I didn't find much, especially o
2013/5/22 Rafał Radecki
> Hi All.
>
> I use mysql/perconna/maria on my production CentOS 6 Linux servers. I
> currently try to choose the default filesystem for partitions with mysql
> data. Some time ago (previous dba) reiserfs was the choice but now it is
> not in the kernel and the main author
Hi All.
I use mysql/perconna/maria on my production CentOS 6 Linux servers. I
currently try to choose the default filesystem for partitions with mysql
data. Some time ago (previous dba) reiserfs was the choice but now it is
not in the kernel and the main author is in prison.
>From what I've read
13 matches
Mail list logo
