On Thu, Dec 22, 2005 at 06:35:24PM -0500, Bruce Momjian wrote:
Hannu Krosing wrote:
?hel kenal p?eval, N, 2005-12-22 kell 18:19, kirjutas Bruce Momjian:
I guess he rather wants to have dont-save-but-execute-immediately
pl/pgsql code.
could this perhaps be solved by having temporary
Of course having the ability to execute arbitrary plpgsql in .sql
scripts would be handy in some cases as well, though as others pointed
out there are alternatives.
I don't know if it's possible. PL/pgSQL parser live in different context
than SQL parser and PostgreSQL supports more languages
I know this is a tech forum and as such, I don't generally plug
products too much. However, EnterpriseDB has anonymous PL/SQL if
you need it.
On 12/22/05, Bruce Momjian pgman@candle.pha.pa.us wrote:
Wow, that is large.I think PL/pgSQL is your best approach.Irecommend you create a schema that users
Jonah H. Harris wrote:
I know this is a tech forum and as such, I don't generally plug products too
much. However, EnterpriseDB has anonymous PL/SQL if you need it.
Interesting. The posting is certainly appropriate. I know Command
Prompt and GreenPlum have been using this loophole. :-)
In
It's implemented in the server with extensions for psql to support it.On 12/23/05, Bruce Momjian pgman@candle.pha.pa.us
wrote:Jonah H. Harris wrote: I know this is a tech forum and as such, I don't generally plug products too
much.However, EnterpriseDB has anonymous PL/SQL if you need
Hi ,
Here is the requirements :
1. Development Support team can ONLY have READ Only ACCESS
to PRODUCTION Database. They will NOT have access to create
stored procedure functions in the PRODUCTION on the fly.
2. During application support, need to write script which
uses procedural
Ashok Agrawal wrote:
Hi ,
Here is the requirements :
1. Development Support team can ONLY have READ Only ACCESS
to PRODUCTION Database. They will NOT have access to create
stored procedure functions in the PRODUCTION on the fly.
2. During application support, need to write
Ühel kenal päeval, N, 2005-12-22 kell 18:19, kirjutas Bruce Momjian:
Ashok Agrawal wrote:
Hi ,
Here is the requirements :
1. Development Support team can ONLY have READ Only ACCESS
to PRODUCTION Database. They will NOT have access to create
stored procedure functions in
Hannu Krosing wrote:
?hel kenal p?eval, N, 2005-12-22 kell 18:19, kirjutas Bruce Momjian:
Ashok Agrawal wrote:
Hi ,
Here is the requirements :
1. Development Support team can ONLY have READ Only ACCESS
to PRODUCTION Database. They will NOT have access to create
I don't need ability to sit at a prompt and type stuff.
To be more clear, I am attaching one sample code. I would like to
migrate this code using postgres without converting into procedure
or function.
Thanks
Ashok
Bruce Momjian wrote On 12/22/05 15:35,:
Hannu Krosing wrote:
?hel kenal
Wow, that is large. I think PL/pgSQL is your best approach. I
recommend you create a schema that users can write into.
---
Ashok Agrawal wrote:
I don't need ability to sit at a prompt and type stuff.
To be more clear,
11 matches
Mail list logo
