I have a need for columns of boolean data to indicate if items in my
database have (or do not have) certain attributes. These are all truly
yes/no values. For Derby what is the best approach for me to take (I have
next to zero database experience so I am not aware of any best practices)?
Thanks for the advice I was leaning towards the numeric solution but using 'T'
/ 'F' as a visual clue makes a lot of sense. After all until we do have a new
boolean data type that visual clue is all we have. I am already looking
forward to the next version:-)
Ian
- Original Message
choice for column's data type to represent boolean data
Thanks for the advice I was leaning towards the numeric solution but using
'T' / 'F' as a visual clue makes a lot of sense. After all until we do have
a new boolean data type that visual clue is all we have. I am already
looking forward
Principal
MSCC
312 952 8175
-Original Message-
From: Bayless Kirtley [EMAIL PROTECTED]
Date: Thu, 7 Dec 2006 09:20:07
To:Derby Discussion derby-user@db.apache.org
Subject: Re: Best choice for column's data type to represent boolean data
Is there reason to think the next version may
Actually I was just opening wishing but I checked the bug database and
found issue 499 https://issues.apache.org/jira/browse/DERBY-499. Looks
like a lot of work was done and it was almost in but had to backed out
http://issues.apache.org/jira/browse/DERBY-1029 because of a blocking
issue
Hi Ian,
Two issues block the introduction of a BOOLEAN datatype:
1) We need DRDA support in order to transport this type across our
network layer. I am cautiously optimistic that we will see this type
appear in the DRDA spec early in 2007. So, soon, this issue will not
block us.
2)
Rick Hillegas wrote:
Hi Ian,
Two issues block the introduction of a BOOLEAN datatype:
1) We need DRDA support in order to transport this type across our
network layer. I am cautiously optimistic that we will see this type
appear in the DRDA spec early in 2007. So, soon, this issue will not
I have a need for columns of boolean data to indicate if items in my database
have (or do not have) certain attributes. These are all truly yes/no values.
For Derby what is the best approach for me to take (I have next to zero
database experience so I am not aware of any best practices)? In
