Re: [HACKERS] UNICODE characters vs. BINARY - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [HACKERS] UNICODE characters vs. BINARY
Date
Msg-id 3855F34F.9B30308E@alumni.caltech.edu
Whole thread Raw
In response to UNICODE characters vs. BINARY  (Gunther Schadow <gunther@aurora.rg.iupui.edu>)
Responses Re: [HACKERS] UNICODE characters vs. BINARY
List pgsql-hackers
> A related question is whether we could support some more
> standard names for data types (e.g., BIGINT, SMALLINT, etc.)
> But I'm not sure there is really any standard. I would be
> willing to work a little on these data types but I'd need
> someone to hint me on who else is doing stuff and, if possible,
> where to look first (and what known mistakes to avoid.)

postgres=> create table x (i smallint);
CREATE
postgres=> create table y (j bigint);
ERROR:  Unable to locate type name 'bigint' in catalog

afaik we support the type names defined in SQL92 (like smallint),
historical names in Postgres, and some extensions. What more do we
need?
                 - Thomas

-- 
Thomas Lockhart                lockhart@alumni.caltech.edu
South Pasadena, California


pgsql-hackers by date:

Previous
From: Michael Robinson
Date:
Subject: Re: [HACKERS] Datatype MONEY
Next
From: Christof Petig
Date:
Subject: Re: [HACKERS] LONG