Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field
Date
Msg-id 46FA8780.9050004@enterprisedb.com
Whole thread Raw
In response to Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field  (Guillaume 'ioguix' de Rorthais <ioguix@free.fr>)
List pgsql-bugs
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field
Next
From: "Michael "Zorkus" Antonov"
Date:
Subject: BUG #3636: createNativeQuery - don't work with INSERT INTO.