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

Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, ioguix <ioguix(at)free(dot)fr>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field
Date: 2007-09-26 16:23:28
Message-ID: 46FA8780.9050004@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
>> I am amused by the fact that we store the sequence name in the sequence
>> itself though.
> 
> Yeah, it's a bit pointless.  One possible response to this gripe would
> be to take the name out of the sequence itself.  However, that would
> likely break client-side code for no very good reason.

Would it be possible to create a SELECT rule on the sequence that
returns the sequence name from the catalog instead?

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2007-09-26 19:22:56
Subject: Re: BUG #3636: createNativeQuery - don't work with INSERT INTO.
Previous:From: Michael Zorkus AntonovDate: 2007-09-26 15:45:56
Subject: BUG #3636: createNativeQuery - don't work with INSERT INTO.

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