DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	b=bVLhnAYlPGm0/FbceAv7UMJOEhIiLCWZidwD7i39NeEtwjv6/Isu1itcrV5rtQmk6m
	2TasO+Tb0Or9H8BJ7SP63eynDqHqzK8yKbN22zNcz925aO4BKBgdcVQw4f3cN6u3UUrw
	I7/cvnYMM4EL95Cf4/HYOTlKs6ooZOP7F/xkU=
MIME-Version: 1.0
Date: Mon, 2 May 2011 12:46:40 +0200
Message-ID: <BANLkTi=8Ws27gAVkQY44gf9OH2j_+kME2w@mail.gmail.com>
Subject: BINARY and BINARY VARYING datatypes in PostgreSQL
From: Grzegorz Szpetkowski <gszpetkowski@gmail.com>
To: pgsql-sql@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1

I know that BIT and BIT VARYING types were deleted from SQL:2003 and
there are "old new" BINARY, BINARY VARYING in SQL:2008. I have two
question:

1) Are these types technically the same (I mean implementation things) ?
2) Is PostgreSQL aim to support BINARY, BINARY VARYING in 9.1 and
leave BIT and BIT VARYING for backward compability (for example as
aliases) ?

"PostgreSQL supports most of the major features of SQL:2008. Out of
179 mandatory features required for full Core conformance, PostgreSQL
conforms to at least 160. In addition, there is a long list of
supported optional features. It might be worth noting that at the time
of writing, no current version of any database management system
claims full conformance to Core SQL:2008."

from: http://developer.postgresql.org/pgdocs/postgres/features.html

Regards,
Grzegorz Szpetkowski