Re: Writing Oracle Stored Procedures in Perl

What is your goal of finding a replacement language for Oracle PL/SQL? Explaining that may help.

Combining Perl and PL/SQL is very powerful as both are excellent languages and both are highly portable. Where there is Oracle (most platforms) there is PL/SQL. Why not use both languages and keep your procedural database code compiled/self-contained in the database as PL/SQL packages?

Are you trying to make your procedural database code vendor agnostic?

Comment on Re: Writing Oracle Stored Procedures in Perl

Replies are listed 'Best First'.
Re^2: Writing Oracle Stored Procedures in Perl by kennethk (Abbot) on Apr 12, 2009 at 05:27 UTC
Our primary motivation is leveraging an existing code-base and experience for internal functions. For example, we would like to migrate some data logic from our loaders, written in Perl, into triggers. Given some of the complexity in our data, using Perl in the data retrieval would be a blessing, but I am cynical about performance (but not prematurely optimizing). This is all underscored by a recent security policy handed down severely restricting what we can use as a front end. In particular, all code running between the database and the outside world must be Java or .NET and all custom code is strongly discouraged. I would like to emphasize we are not munging up display and data logic - I'm talking about ranking/grouping, complex constraints, ...	[reply]

Replies are listed 'Best First'.

Re^2: Writing Oracle Stored Procedures in Perl
by kennethk (Abbot) on Apr 12, 2009 at 05:27 UTC

This is all underscored by a recent security policy handed down severely restricting what we can use as a front end. In particular, all code running between the database and the outside world must be Java or .NET and all custom code is strongly discouraged. I would like to emphasize we are not munging up display and data logic - I'm talking about ranking/grouping, complex constraints, ...

[reply]