Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 


 
     
Recent Posts
   
Popular Topics
Home   
Search
    Members    Calendar    Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Prakriti Agrawal » Bit by bit
Add to briefcase
29 posts, Page 3 of 3
«««123

Bit by bit Expand / Collapse
Rate Topic
Display Mode
Topic Options
Author
Message
bhakti-sonu
Posted Thursday, January 28, 2010 10:05 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, March 12, 2010 3:15 AM
Points: 66, Visits: 78
I try this out with @bit = 0 it gives message "no"
if @bit = -500 ,it gives message "yes",
if @bit = -1 then also it gives "yes".

The Explanation Given for Answer : Bit constants are represented by the numbers 0 or 1, if a number larger than one is used, it is converted to one.
but what about the values less than 1, still they consider as 1

Please explain me more about the negative values used for bit datataype.
Post #855758
alpeshgediya
Posted Thursday, January 28, 2010 10:15 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, March 25, 2013 7:14 AM
Points: 196, Visits: 60
for bit datatype, any value which in non-zero is converted to bit 1.

try this you will get better understading,

declare @bit bit
set @bit = -0
select @bit

declare @bit bit
set @bit = +0
select @bit

as mathematical there is no concept of +/- 0 ..is for only understading purpose.
Post #855762
ChiragNS
Posted Sunday, January 31, 2010 10:24 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Wednesday, April 24, 2013 5:02 AM
Points: 2,365, Visits: 1,825
why is'nt BIT treated like other datatypes?

"Keep Trying"
Post #856934
Marry Krissmess
Posted Friday, February 05, 2010 5:12 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, April 25, 2013 2:25 PM
Points: 94, Visits: 29
Bob Cullen-434885 (1/28/2010)
OK. I am in the 17% who got it wrong - I replied "Error". And now I know. But will somebody kindly explain why BIT is treated any differently to TINYINT, SMALLINT, INT, etc. It is, after all, only a type that has a range of valid values. If the others report an overflow error when I try to assign values outside their permitted range, why not BIT also?


I am exactly feeling the same. I think a database should not be so forgiving. In programming languages this may be treated as boolean but here it should be a numeric range and any thing else than 0 or 1 should throw an error.
Post #860936
Toreador
Posted Monday, February 08, 2010 2:02 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 17, 2013 9:52 AM
Points: 1,356, Visits: 4,761
Marry Krissmess (2/5/2010)
In programming languages this may be treated as boolean but here it should be a numeric range and any thing else than 0 or 1 should throw an error.


Why? The Bit datatype is a boolean, so why is it so surprising that it is treated as such?
Post #861483
Paul White
Posted Tuesday, March 30, 2010 10:13 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:43 PM
Points: 10,989, Visits: 10,533
Marry Krissmess (2/5/2010)
I am exactly feeling the same. I think a database should not be so forgiving. In programming languages this may be treated as boolean but here it should be a numeric range and any thing else than 0 or 1 should throw an error.

Try it with the strings 'true' and 'false' - that will really upset you!


Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #893006
Paul White
Posted Tuesday, March 30, 2010 10:14 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:43 PM
Points: 10,989, Visits: 10,533
ChiragNS (1/31/2010)
why is'nt BIT treated like other datatypes?

It is. The value supplied is implicitly converted to a BIT, according to the conversion rules.


Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #893008
shini2007
Posted Thursday, September 16, 2010 11:46 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, October 26, 2012 12:30 PM
Points: 20, Visits: 27
I think":
" Converting to bit promotes any nonzero value to 1" not greater than zero only Because

DECLARE @bit BIT
SET @bit = -14

IF @bit = 1PRINT 'yes'ELSE PRINT 'no'

is also give yes.
Post #987900
Paul White
Posted Friday, September 17, 2010 1:32 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 8:43 PM
Points: 10,989, Visits: 10,533
shini2007 (9/16/2010)
I think":" Converting to bit promotes any nonzero value to 1" not greater than zero only Because

DECLARE @bit BIT
SET @bit = -14

IF @bit = 1PRINT 'yes'ELSE PRINT 'no'

is also give yes.

Non-zero does not mean greater than zero, it means not zero.
-14 is not zero, so it is converted to 1, as I said.
Does that make sense?


Paul White
SQL Server MVP
SQLblog.com
@SQL_Kiwi
Post #987934
« Prev Topic | Next Topic »

Add to briefcase
29 posts, Page 3 of 3
«««123

Permissions Expand / Collapse

 
 
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.