Re: Proposed patch for sequence-renaming problems
От | Tom Lane |
---|---|
Тема | Re: Proposed patch for sequence-renaming problems |
Дата | |
Msg-id | 786.1127875130@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Proposed patch for sequence-renaming problems (Bruce Momjian <pgman@candle.pha.pa.us>) |
Ответы |
Re: Proposed patch for sequence-renaming problems
|
Список | pgsql-patches |
Bruce Momjian <pgman@candle.pha.pa.us> writes: > I looked over the patch, and while it does fix the problem for SERIAL, I > am concerned about expecting users to user ::regclass in normal usage, > and I am concerned about adding something we will have to support in the > future when we come up with a better solution. Why is regclass not > being used automatically? If we provide both nextval(text) and nextval(regclass), then the parser will interpret "nextval('something')" as nextval(text) because that's the more preferred resolution of an unknown-type literal. The only way to make regclass be used "automatically" would be to remove the text-input variant. That is where I want to go eventually, but it seems pretty risky to jump there in one step. The proposed patch adds regclass-based functions alongside the existing functionality, so that people can migrate as they choose; it does not open any risks of breaking cases that work now. regards, tom lane
В списке pgsql-patches по дате отправления: