Re: Porting from PL/SQL to PLPGSQL - Mailing list pgsql-sql

From Jomon Skariah
Subject Re: Porting from PL/SQL to PLPGSQL
Date
Msg-id F83B457BE363174B8233DE042A1445703E2412@maya.aztec.soft.net
Whole thread Raw
In response to Porting from PL/SQL to PLPGSQL  (Jomon Skariah <jomons@aztec.soft.net>)
List pgsql-sql

Hi Josh,

Thanks for your reply.

In our PL/SQL code we have used userenv('LANG') in some of the INSERT
statements.
Do we have a replacement for this..

Regards

Jomon





-----Original Message-----
From: Josh Berkus [mailto:josh@agliodbs.com]
Sent: Thursday, August 14, 2003 1:05 AM
To: Jomon Skariah; pgsql-sql@postgresql.org
Subject: Re: [SQL] Porting from PL/SQL to PLPGSQL


Jomon,

> 1)     In Exceptions ORACLE have something called WHEN OTHERS THEN cluase.I
> can't find a replacement for that in 
>             PostGreSQL.

PL/pgSQL currently does not handle exceptions at all.  This is on the TODO 
list.

> 2    Oracle have a function USERENV to get the user session
> information.Is there any replacement available in PostGres. ?

There are several variables and tools which provide current user and session

information.  See the "PostgreSQL Administration" section of the 
documentation.

> 3    Is there any replace available for INSTEAD OF INSERT/DELETE/UPDATE
> for triggers in PostGreSQL.

In Postgres, this is generally done through the RULES system instead of 
triggers.  Please lookup CREATE RULE in the online docs.

-- 
-Josh BerkusAglio Database SolutionsSan Francisco


pgsql-sql by date:

Previous
From: "Slawek Jarosz"
Date:
Subject: Optional join
Next
From: Bruno Wolff III
Date:
Subject: Re: Optional join