From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
Cc: | Mamatha_Kagathi_Chan(at)DELL(dot)com, haramrae(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: [pgadmin-support] Help for Migration |
Date: | 2011-12-07 13:33:59 |
Message-ID: | 1323264839.2244.36.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support pgsql-general |
On Wed, 2011-12-07 at 14:30 +0100, Guillaume Lelarge wrote:
> On Wed, 2011-12-07 at 21:23 +0800, Craig Ringer wrote:
> > On 12/07/2011 06:57 PM, Mamatha_Kagathi_Chan(at)DELL(dot)com wrote:
> > [...]
> > > I can also get the same result if I execute it in pgadmin (version downloaded from postgres community) which is on a different client machine but connected to the server on enterpriseDB version
> > > As EXEC proc.
> > If you're connected to EnterpriseDB, I'd expect that.
> >
> > If you're connected to PostgreSQL, maybe PgAdmin is translating EXEC
> > into a SELECT ?
> >
>
> pgAdmin doesn't translate queries executed by the user. If EXEC works on
> EDB AS, then pgadmin will fire it with success. If it doesn't, pgadmin
> will fire it, and the result will be a failure.
>
BTW, pgAdmin allows to open the query tool with an EXEC script when the
user has selected a procedure (EDB AS object). So I guess EDB AS
supports the EXEC statement :)
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Mamatha_Kagathi_Chan | 2011-12-08 06:10:14 | Re: [pgadmin-support] Help for Migration |
Previous Message | Guillaume Lelarge | 2011-12-07 13:30:22 | Re: [pgadmin-support] Help for Migration |
From | Date | Subject | |
---|---|---|---|
Next Message | akp geek | 2011-12-07 14:03:28 | postgres 9.0.4 Streaming relate question .. |
Previous Message | Guillaume Lelarge | 2011-12-07 13:30:22 | Re: [pgadmin-support] Help for Migration |