Skip site navigation (1) Skip section navigation (2)

RE: New SQL Datatype RECURRINGCHAR

From: "David Bennett" <dbennett(at)bensoft(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Rod Taylor" <rbt(at)barchord(dot)com>
Cc: <dbennett(at)jade(dot)bensoft(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: New SQL Datatype RECURRINGCHAR
Date: 2001-07-06 22:44:21
Message-ID: NEBBIHDFALGPGDHNLKBBOEHPCJAA.dbennett@bensoft.com (view raw or flat)
Thread:
Lists: pgsql-hackers
The only problem with 'enum' is that all of the possible values must be
specified at CREATE time.  A logical extension to this would be to allow for
'dynamic extensions' to the list.

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Tuesday, July 03, 2001 4:49 PM
To: Rod Taylor
Cc: dbennett(at)jade(dot)bensoft(dot)com; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] New SQL Datatype RECURRINGCHAR


"Rod Taylor" <rbt(at)barchord(dot)com> writes:
> This is rather like MySQL's enum.

Yes.  If we were going to do anything like this, I'd vote for stealing
the "enum" API, lock stock and barrel --- might as well be compatible.

			regards, tom lane


In response to

pgsql-hackers by date

Next:From: Naomi WalkerDate: 2001-07-06 22:51:44
Subject: 2 gig file size limit
Previous:From: Bruce MomjianDate: 2001-07-06 21:59:46
Subject: Re: [GENERAL] Vacuum and Transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group