Join | Login | Why Join?   
SQL Server, Oracle, DB2, Sybase, MySQL Help - SSWUG.ORG HACKER SAFE certified sites prevent over 99.9% of hacker crime.
Search SSWUG:   
 
Access to 492 free guest articles, discussions and more, just create your free SSWUG User ID:
Email address:  
This will be your login ID - we'll email you your password - you'll even receive the newsletter, opt-out at any time.
Email to Friend //  Discuss Article //  Rate Article //  Digg Article //  Add to Del.icio.us //  Add to Technorati

 

BitMask Fields

Available for Members. This is an off-site link.  Please review our Terms of Service (bottom of page) for additional information.


 Article Abstract:

This blog post is in response to one of the questions that we got from our reader. Here is the question:

“I’d like to hear your opinions on bitmask fields. I have found a lot of flames on using bitmask fields into RDBMS and most of them look a lot like the cons of EAV models, which I do agree (I just learned it the hard way, after using this design in a system which later became real hell), but what are the cons in bitmask fields when we just need an “open” set of boolean flags? Apart from indexing (which I believe would be impossible to be done) would it be better to add a new bit field for every new flag to your existing databases than using a bitmask field?”

 Read this article...



Key (Please note):
(R) - registration may be required for access at the target site
($) - target site may require paid membership for access to this or other content


No Comments/Feedback Posted Yet. Post Your Comments/Feedback

Email to Friend //  Discuss Article //  Rate Article //  Digg Article //  Add to Del.icio.us //  Add to Technorati

   




 

[ Register ] [ Webcasts ] [ Podcasts ] [ Newsletter Archive ] [ RSS/Feeds ]
[ About ] [ Advertise ] [ Contact ] [ Privacy ] [ Terms of Service ]
[ Link to SSWUG ] [ List Server Archives ] [ Recent Orig. Content ]
(c) 1997-2008, Bits on the Wire, Inc.  (0)

Some names and products covered by SSWUG are the registered trademarks of their respective owners.
DAA10354WWW004