Re: PL/SQL vs. Java

    I would plan a few prototype projects to see what the problems are with programming in each of the languages for your development team and programming goals. Basically pick some simple exercises that are interesting to your ultimate project and implement them in both languages.

    Some things to measure:

    (1) How often do you need to call customer support to get simple code to run? How long do you spend with customer support to get a solution?

    (2) Which code runs quickest? Since speed is likely your concern, which slows you down more, Java or PLSQL?

    I would also try to avoid basing a decision on anything other than measurable results, such as "safety" or "leading-edge" arguments. These are often just disguised marketing influences.

    And if you get interesting measurements you might share them with the newsgroup to see how others might critique the measurements.

    Frank Hubeny

dwilliams_at_lifetouch.com wrote:

> We have a development issue. We are doing some significant Microsoft-
> based client-server development, connecting to an Oracle 8i database on
> a Unix server. We are quickly seeing the drawback to running everything
> on the client. For server-side development, we are trying to decide
> whether to use PL/SQL or Oracle's newer Java-based tools. PL/SQL seems
> the safe mature choice, and Java the slightly more leading-edge choice.
> We are looking for any input on the issues we will face in integrating
> Microsoft and Oracle and which language would be the better choice for
> the future, since we don't have a significant investment in code or
> skills at this point.
>
> Thank you for your opinions.
> Dennis Williams
> DBA
> Lifetouch, Inc.
> Minneapolis, MN
> dwilliams_at_lifetouch.com
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Jun 07 2000 - 00:00:00 CDT