Re: front-end vs back-end

From: Larry Fishman <larryf_at_teleport.com>
Date: 29 Nov 1994 08:13:02 -0800
Message-ID: <3bfjue$fe7_at_sandra.teleport.com>


Tony Jambu (TJambu_at_vtrlmel1.trl.oz.au) wrote:

: In article <3avt24$6bo_at_panix.com>, janest_at_panix.com (John Anest) says:

: >
: >
: > We're wondering if we're the only ones writing a complex financial
: >system entirely on the back-end using stored procedures. We have thousands
: >of lines of code. We cannot keep our transactions short because they're
: >long!
: > Is everybody using the client to process the data? Are you only using
: >the database as a data repository? Is this the reality of the situation?
 

: John
-- snip --

We have been using PowerBuilder as a front end to Oracle for about 4 months. I have found that most of the SQL used is initially attempted from PB and if it requires any level of sophistication at all (by this I mean doing any requery based on the first, etc.), it becomes a PL/SQL procedure, function, etc. We have not done any preformance testing of this even though part of the reason to do this is to cut down on network traffic. The other reason is to create re-usable procedure blocks but not to go hog wild and make every thing a procedure of some sort. It's been sort of a balancing act between the traditional control of main-framer programming style versus wide open freedom of PCs. (This is said without trying to offend anybody - I am not trying to start a flame war) It has been useful.

As an aside, one of the products we use is SQL*Studio to write PL/SQL. It is a PC Windows based tool which has been helpful.

Larry.

-- 
larryf_at_teleport.COM 
Received on Tue Nov 29 1994 - 17:13:02 CET

Original text of this message