...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of David G. Johnston
Sent: Thursday, 5 May 2016 2:06 PM
To: dandl
Cc: Postgres General
Subject: Re: [GENERAL] CREATE OR REPLACE AGGREGATE -- NOT!
On Wednesday, May 4, 2016, dandl mailto:da...@andl.org> >
wrote:
On Wednesday, May 4, 2016, dandl wrote:
> I was surprised to discover that
>
> · CREATE OR REPLACE AGGREGATE is not allowed, but
>
> · CREATE OR REPLACE FUNCTION works just fine
>
>
>
> Is this an oversight, or is there some reason I missed?
>
>
Its not an oversight: but whether
I was surprised to discover that
* CREATE OR REPLACE AGGREGATE is not allowed, but
* CREATE OR REPLACE FUNCTION works just fine
Is this an oversight, or is there some reason I missed?
Yes, I know I can do:
DROP AGGREGATE IF EXISTS
CREATE AGGREGATE
But this triggers a
On 12/15/11, Merlin Moncure wrote:
> On Thu, Dec 15, 2011 at 11:29 AM, Robert James
> 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
On Thu, Dec 15, 2011 at 11:29 AM, Robert James 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
Is there anyway to do the equivalent of CREATE OR REPLACE AGGREGATE?
Or - maybe even better - CREATE AGGREGATE if it doesn't already exist?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
