Re: Replacing SQL with perl

Currently what I do on Oracle 8i is I create the stuff like joins, complex updates and some others as DataBase Proceedures. Then I can call them inside my SQL code. On out putting this data I try to let my SQL handle ordering and such (because the database is faster at it, let's face it: that is its job.) Plus our DB machines are twice as everything of our Web servers.

I believe using these proceedures answers yes to all your questions. This is even more true when it is run many times.

--BigJoe

Learn patience, you must.
Young PerlMonk, craves Not these things.
Use the source Luke.

Comment on Re: Replacing SQL with perl

Replies are listed 'Best First'.
Re: Re: Replacing SQL with perl by Anonymous Monk on Dec 07, 2000 at 01:02 UTC
whoa there! ORDER BY makes almost any Database, especially Oracle, crawl. And if you have multiple app servers, you might want to do your sorting outside the database. depends of course, but ORDER BY is a killer.	[reply]
Re: Re: Re: Replacing SQL with perl by extremely (Priest) on Dec 07, 2000 at 14:39 UTC
Not if the indexes are set up correctly. Anything you ORDER BY on often enough to optimize, optimize with an index. -- $you = new YOU; honk() if $you->love(perl)	[reply]