I tend to stick with 1's and 0's just because they are traditionally used in
programming/mathematics and elsewhere(digital circuit theory). I also think
that 1's and 0's are easier to understand to anyone looking at the code
(i.e. someone who understands a different language).
Shane Witbeck
Webmaster
-----Original Message-----
From: Rob Keniger [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 30, 2000 9:19 PM
To: CF-Talk
Subject: Boolean data was Re: Datatype Mismatch in Access
on 31/10/00 11:21 AM, Gary Davidson at [EMAIL PROTECTED] wrote:
> MS databases perform accordingly. I always use integer to represent
Booleans
> in SQL because Booleans aren't as flexible.
I'm interested as to what is the most efficient way to store boolean values
when not using an actual boolean data type.
Some people seem to use the integer data type to store 1s and 0s, while
others use a char(1) and store "y","n" etc.
What is more efficient/faster when it comes to queries?
--
Rob Keniger
big bang solutions
<mailto:[EMAIL PROTECTED]>
<http://www.bigbang.net.au>
----------------------------------------------------------------------------
--------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a
message with 'unsubscribe' in the body to [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
