User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.159 Safari/535.1
Would it be viable to implement BIT (as bit) and BIT VARYING (maybe as smallest possible fixed datatype given the precision)?
I'm currently using the very easy workaround using the example below, but I guess using the datatypes and operators (4.3.2) designed for this might be a better idea.
cast(power(2, dayofweek(cast('2012-02-15' as date))) as smallint))
Bit and bitvarying datatypes are also common in astronomy.
No test needed for feature request
According to https://en.wikipedia.org/wiki/SQL:2003
the data types "BIT" and "BIT VARYING" have been removed from SQL:2003 standard.
See line: "removal of the poorly implemented "BIT" and "BIT VARYING" data types".
(In reply to Martin van Dinther from comment #3)
> According to https://en.wikipedia.org/wiki/SQL:2003
> the data types "BIT" and "BIT VARYING" have been removed from SQL:2003
> See line: "removal of the poorly implemented "BIT" and "BIT VARYING" data
Again a reason why it should have been implemented before ;) But since it is in PostgreSQL I find it a good reason to be feature matching.