Re: Pro*C vs. PL/SQL

From: Steve Baker <bakes_at_corona.iinet.net.au>
Date: 1996/01/18
Message-ID: <30FE0BC5.5C2CE7C1_at_corona.iinet.net.au>#1/1


Kevin Merritt wrote:
>
> I would like anybody's thoughts on the advantages and/or
> disadvantages of developing robust applications in PRO*C
> vs. PL/SQL.
>
> We are porting a mature, robust COBOL application to Oracle
> and would like to choose the right long-term development
> tool.
>
> Specifically, I'd like feedback comparing PRO*C with PL/SQL
> on the following areas:
>
> Performance
> Learning Curve
> Long Term Maintainability
> Time of Development
>
> For purposes of this comparison, assume that our staff is
> comprised of strong C programmers who have no knowledge of
> either PRO*C or PL/SQL.
>
> I appreciate your feedback in advance.
>
> Kevin Merritt

I think that you should learn both - keep some PL/SQL procedures and functions in the database, which you can call from PRO*C (or run as database triggers) - these will be most efficient for most situations.

However there are some things that PL/SQL just won't do (although apparently the next release will do much more) so use PRO*C for these bits.

Performance for computation is quicker for PRO*C, but database performance is better for PL/SQL. Learning curve is about equal for both given your givens, and they come out equal on the rest.

Use both. The best part is you can embed PL/SQL code in your PRO*C programs, to get the best of both worlds in just one of those worlds.

-- 
Steve Baker,  aka  bakes_at_corona.iinet.net.au
Your limitations are restricted by your goals, not the other way around.
Received on Thu Jan 18 1996 - 00:00:00 CET

Original text of this message