Yea, you're right. I goofed. I even was wrong about how it is in C... it
is actually 1=true and everything else is false. I must be losing it.
Brandon Goodin wrote:
Generally when representing a boolean as a CHAR in the database
0=false and 1 and greater = true. But, with my stuff it's more like
Generally when representing a boolean as a CHAR in the database
0=false and 1 and greater = true. But, with my stuff it's more like 1
= true and everything else is false. But, i usually stick to looking
for '0' or '1' in my code for explicit and then assuming false if it
is anything other. Also ano
Having 0 = true seems to me to be the opposite of what I would ever expect...
--- Mike Zatko <[EMAIL PROTECTED]> wrote:
> I have a db table that has a field that has a SMALLINT datatype. This
> field is being used as a true/false flag. 0 would be true, anything else
> would be false as would typ
You should use a custom type handler for conversion from text to boolean.
We'll be including a standard one in a future release.
Clinton
On Fri, 25 Mar 2005 10:20:46 -0500, Mike Zatko <[EMAIL PROTECTED]> wrote:
> I have a db table that has a field that has a SMALLINT datatype. This
> field is b
I have a db table that has a field that has a SMALLINT datatype. This
field is being used as a true/false flag. 0 would be true, anything else
would be false as would typically happen in C. I set up a result map
that looks like the following:
I was thrilled that it worked, but
5 matches
Mail list logo
