Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field
От | Guillaume 'ioguix' de Rorthais |
---|---|
Тема | Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field |
Дата | |
Msg-id | 4701622F.9030101@free.fr обсуждение исходный текст |
Ответ на | Re: BUG #3619: Renaming sequence does not update its 'sequence_name' field (Heikki Linnakangas <heikki@enterprisedb.com>) |
Ответы |
Re: BUG #3619: Renaming sequence does not update its 'sequence_name'
field
|
Список | pgsql-bugs |
Heikki Linnakangas a écrit : > 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. 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 this issue. 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
В списке pgsql-bugs по дате отправления: