Joe Breeden queried:
It would be interesting to know how other people have solved
that problem.
Currently, we are essentially using embedded SQL in our apps.
I have found that stored procedures + perl module wrapper around the procs.
is a nice, balanced approach.
The procs. give a nice
Homsher, Dave V. writes:
Joe Breeden queried:
It would be interesting to know how other people have solved
that problem.
Currently, we are essentially using embedded SQL in our apps.
I have found that stored procedures + perl module wrapper around the procs.
is a nice,
All
Joe Breeden queried:
It would be interesting to know how other people have solved
that problem.
Currently, we are essentially using embedded SQL in our apps.
I have found that stored procedures + perl module wrapper around the
procs.
is a nice, balanced approach.
Definitely; sotred
I have found that stored procedures + perl module wrapper around the
procs.
is a nice, balanced approach.
The procs. give a nice performance boost as they are precompiled into
the
server (we use Sybase).
They are definitely faster, and significantly so.
Maybe so for Sybase. In
Perrin Harkins writes:
I have found that stored procedures + perl module wrapper around the
procs.
is a nice, balanced approach.
The procs. give a nice performance boost as they are precompiled into
the
server (we use Sybase).
They are definitely faster, and
It would be interesting to know how other people have solved
that problem.
Currently, we are essentially using embedded SQL in our apps.
I have found that stored procedures + perl module wrapper
around the
procs.
is a nice, balanced approach.
Definitely; stored procedures are hit-and-miss
On Wed, 1 Aug 2001, Kyle Dawkins wrote:
KD Definitely; sotred procedures are hit-and-miss in a lot of
KD environments. Remember that a large number of people in the
KD mod_perl world can't use 'em because they (we) use MySQL. If one
KD wanted to emulate this behaviour with MySQL, you would
Original Message
Subject: Re: Not embedding SQL in perl
Date: Wed, 01 Aug 2001 15:56:00 -0400
From: kyle dawkins [EMAIL PROTECTED]
To: Henrik Edlund [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Henrik Edlund wrote:
And while we are discussing not cutting corners, those
On Wed, 1 Aug 2001, kyle dawkins wrote:
kd Not sure if you're aware of it, but that argument is pretty old.
kd We're onto a much more interesting, new argument now. :-)
All old arguments eventually becomes new again, once in a while... :-)
kd Seriously though, you're right, MySQL is not a real
: Not embedding SQL in perl
Date: Wed, 01 Aug 2001 15:56:00 -0400
From: kyle dawkins [EMAIL PROTECTED]
To: Henrik Edlund [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Henrik Edlund wrote:
And while we are discussing not cutting corners, those who still use
MySQL should switch to a real DBMS
Jon
I can see your arguement regarding SQL within one's code, but doesn't
your arguement fail to hold up if we assume that the SQL is fully
compliant?
Well, yes and no. I was citing that example as *another* reason to keep
SQL out of your application-level code.
If you do, as Henrik
On Wed, 1 Aug 2001, Kyle Dawkins wrote:
KD Definitely; sotred procedures are hit-and-miss in a lot of
KD environments. Remember that a large number of people in the
KD mod_perl world can't use 'em because they (we) use MySQL. If one
KD wanted to emulate this behaviour with MySQL, you would
On Wed, 1 Aug 2001, kyle dawkins wrote:
kd Well, yes and no. I was citing that example as *another* reason to keep
kd SQL out of your application-level code.
kd If you do, as Henrik suggests, write pure SQL92, then obviously you
kd wouldn't need to wrap all your SQL in ifs like they did with
kd
On Thu, 2 Aug 2001, Gunther Birznieks wrote:
When you've had your fill of wrestling over mySQL vs PostGres and stored
procs versus inline SQL (I know I have long ago)
You guys should definitely read the following:
http://www.ambysoft.com/persistenceLayer.html
One of my current
At 02:44 PM 8/1/2001 -0700, Jeffrey W. Baker wrote:
On Thu, 2 Aug 2001, Gunther Birznieks wrote:
When you've had your fill of wrestling over mySQL vs PostGres and stored
procs versus inline SQL (I know I have long ago)
You guys should definitely read the following:
15 matches
Mail list logo
