Hi all!
I have to convert functions and procedures from Oracle to PostgreSQL. I
looked at all the stuff of the Pg-Homepage and I ask me if there are any
tools, that support the conversion.
Writing PS/PGSQL tools seems to be a bit hard, because of the existing
tool-infrastructure on linux. Ar
Am Donnerstag, 10. Mai 2001 19:23 schrieb Roberto Mello:
> On Thu, May 10, 2001 at 03:33:27PM +0200, Klaus Reger wrote:
> Have you looked at the "Porting From Oracle PL/SQL" chapter of the
> PostgreSQL Programmer's Guide? I am expanding that guide to include more
>
Hi all!
I have to convert functions and procedures from Oracle to PostgreSQL. I
looked at all the stuff of the Pg-Homepage and I ask me if there are any
tools, that support the conversion.
Writing PS/PGSQL tools seems to be a bit hard, because of the existing
tool-infrastructure on linux. Ar
Hi,
I want to learn, how the pl/plsql-parser/compiler works. Therefore I planned
to implement a simple ELSIF, like oracle does.
I added the following K_ELSIF branch to gram.y, in the hope that, when ELSIF
is parsed, simply another if-structure in inserted.
Hi all,
because no one noticed my last question, please forgive me this repost, but I
promised my boss to get an answer to this questions.
Here they are:
When a new table or field is created without quotes, it is assumed to be
case-insensitive. Herefore I have some questions:
- Is it SQL-92-c
On Tuesday, 10. July 2001 11:45, you wrote:
> > When a new table or field is created without quotes, it is assumed to be
> > case-insensitive. Herefore I have some questions:
> >
> > - Is it SQL-92-conform to handle >"test"< like >test< without quotes, or
> > shouldn't it be >test< forced to lower
On Wednesday, 11. July 2001 17:28, you wrote:
> Mike Mascari writes:
> > MESSAGE ON INDEX i_employees IS
> > 'An employee with a matching Social Security number already exists';
> >
> > Then, when the UNIQUE constraint of the index is violated, instead of
> > the message:
> >
> > 'Cannot insert a
