Heikki Linnakangas a écrit :
> 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.
Actually, there's at least one reason : client side code using this value is buggy when a sequence is renamed.
That's exactly how I found this issue: when coding "alter sequence" stuff in ppa which was using it...
Presently, I will not use this value anymore, but I think other dev / projects which are using it should be inform about
However, I don't know if breaking client side code is the solution neither.
> Would it be possible to create a SELECT rule on the sequence that
> returns the sequence name from the catalog instead?
Well it looks a pretty good idea to me, but I'm not really aware about internal constraints to judge :S
In response to
pgsql-bugs by date
|Next:||From: Eric Haszlakiewicz||Date: 2007-10-02 08:07:05|
|Subject: Re: BUG #3645: regular expression back references seem broken|
|Previous:||From: Kevin Grittner||Date: 2007-10-01 19:23:59|
|Subject: Re: Question about PostGreSQL|