sorry,
I guess I meant that, when using CF, I have never had issues with No or False
or 0 being read as the same by the SQL Server
>No it doesn't.
>
>Here is an example on SQL 2005:
>
>declare @test table (
> testVal bit
>)
>
>insert into @test (testval) values (0);
>insert into @test (testval) values ('Yes'); -- Results in error
>Conversion failed when converting the varchar value 'Yes' to data type
>bit.
>insert into @test (testval) values ('True'); -- Results in error
>Conversion failed when converting the varchar value 'True' to data type
>bit.
>insert into @test (testval) values ('No'); -- Results in error
>Conversion failed when converting the varchar value 'No' to data type
>bit.
>insert into @test (testval) values ('False'); -- Results in error
>Conversion failed when converting the varchar value 'False' to data type
>bit.
>
>select * from @test
>
>Sql expects data types that match. ColdFusion isn't strongly typed so
>false and no are equivalent to 0.
>
>Steve
>
>
>
>SQL will read a NO or FALSE or 0 as the same
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:342439
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
