From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Gunther Schadow <gunther(at)aurora(dot)rg(dot)iupui(dot)edu> |
Cc: | "hackers(at)postgreSQL(dot)org" <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] UNICODE characters vs. BINARY |
Date: | 1999-12-14 07:35:43 |
Message-ID: | 3855F34F.9B30308E@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 1999-12-14 08:54:54 | Questionable codes |
Previous Message | Michael Robinson | 1999-12-14 04:20:21 | Re: [HACKERS] Datatype MONEY |