Re: CREATE OR REPLACE AGGREGATE
От | Merlin Moncure |
---|---|
Тема | Re: CREATE OR REPLACE AGGREGATE |
Дата | |
Msg-id | CAHyXU0wnKG0MZ+FrKZmHLZYsKhZZcmR28Go6gOMf4y4uM_Ms+g@mail.gmail.com обсуждение исходный текст |
Ответ на | CREATE OR REPLACE AGGREGATE (Robert James <srobertjames@gmail.com>) |
Ответы |
Re: CREATE OR REPLACE AGGREGATE
|
Список | pgsql-general |
On Thu, Dec 15, 2011 at 11:29 AM, Robert James <srobertjames@gmail.com> wrote: > Is there anyway to do the equivalent of CREATE OR REPLACE AGGREGATE? > Or - maybe even better - CREATE AGGREGATE if it doesn't already exist? Well, you have DROP [IF EXISTS] which should cover at least some of the use cases. I'm not sure a OR REPLACE for aggreates is a good idea -- you can already REPLACE the internal function (which is mostly what you need). The aggregate itself mainly defines the input types, state, and output types. The main advantage of replace is you get to preserve the oid and avoid dependency issues -- if you are changing the aggregate, it's pretty likely you'd have to go through that anyways. merlin
В списке pgsql-general по дате отправления: