Received: from localhost (maia-3.hub.org [200.46.204.184])
	by postgresql.org (Postfix) with ESMTP id 23C059FB546
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 25 Jul 2007 23:35:50 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024)
	with ESMTP id 69125-01 for <pgsql-docs-postgresql.org@postgresql.org>;
	Wed, 25 Jul 2007 23:35:37 -0300 (ADT)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.5
Received: from mtao01.charter.net (mtao01.charter.net [209.225.8.186])
	by postgresql.org (Postfix) with ESMTP id B886F9FB514
	for <pgsql-docs@postgresql.org>; Wed, 25 Jul 2007 23:35:46 -0300 (ADT)
Received: from aa04.charter.net ([10.20.200.156]) by mtao01.charter.net
	(InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP
	id <20070726023545.DNEJ1445.mtao01.charter.net@aa04.charter.net>
	for <pgsql-docs@postgresql.org>; Wed, 25 Jul 2007 22:35:45 -0400
Received: from [10.0.1.3] (really [66.188.165.91]) by aa04.charter.net
	with ESMTP id <20070726023545.CVYH1254.aa04.charter.net@[10.0.1.3]>
	for <pgsql-docs@postgresql.org>; Wed, 25 Jul 2007 22:35:45 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: quoted-printable
Message-Id: <05510444-AACD-4FE4-9509-3BC3A4DA4526@seespotcode.net>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed
To: pgsql-docs@postgresql.org
From: Michael Glaesemann <grzm@seespotcode.net>
Subject: BIGINT is in apparently SQL:2003
Date: Wed, 25 Jul 2007 21:35:39 -0500
X-Mailer: Apple Mail (2.752.2)
X-Chzlrs: 0
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200707/11
X-Sequence-Number: 4338

Hello!

According to the developers docs

http://developer.postgresql.org/pgdocs/postgres/datatype-=20
numeric.html#DATATYPE-INT

> SQL only specifies the integer types integer (or int) and smallint. =20=

> The type bigint, and the type names int2, int4, and int8 are =20
> extensions, which are shared with various other SQL database systems.

In the SQL:2003 draft I have (ISO/IEC 9075-2:2003 (E)), BIGINT is =20
listed as well as SMALLINT and INT.

> 4.1.2 Naming of predefined types
> SQL defines predefined data types named by the following <key =20
> word>s: CHARACTER, CHARACTER
> VARYING, CHARACTER LARGE OBJECT, BINARY LARGE OBJECT, NUMERIC, =20
> DECIMAL,
> SMALLINT, INTEGER, BIGINT, FLOAT, REAL, DOUBLE PRECISION, BOOLEAN, =20
> DATE, TIME,
> TIMESTAMP, and INTERVAL.

And in "6.1  <data type>"

> 23)SMALLINT, INTEGER, and BIGINT specify the data type exact =20
> numeric, with scale of 0 (zero) and binary or decimal precision. =20
> The choice of binary versus decimal precision is implementation-=20
> defined, but the same radix shall be chosen for all three data =20
> types. The precision of SMALLINT shall be less than or equal to the =20=

> precision of INTEGER, and the precision of BIGINT shall be greater =20
> than or equal to the precision of INTEGER.

There are references

I thought the SQL conformance page could be updated too

http://developer.postgresql.org/pgdocs/postgres/features-sql-=20
standard.html

> E011-01	Core	INTEGER and SMALLINT data types=09

but it appears that the BIGINT language doesn't yet appear in E011-01 =20=

Core: it reads the same as in the docs. The BIGINT feature is =20
referred to as Feature T071 =93BIGINT data type=94. There are references =
=20
that BIGINT should correspond to C's long long (13.6  Data type =20
correspondences), so PostgreSQL conforms on that point as well.

I don't know when I'll get around to submitting a doc patch for this, =20=

but I wanted to at least put it to the list.

Michael Glaesemann
grzm seespotcode net