[EMAIL PROTECTED] (Jeffrey W. Baker) wrote:
>I've worked with Scott Ambler, and I could record everything Scott Ambler
>knows about actually devleloping large systems on the head of a pin, using
>a magic marker. That guy is a hopeless academic without the slightest
>clue of how to actually make s
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:
> >
> >
Yeah!
Go Gunther. This is one of the better articles on persistence... Scott
Ambler has tons of good stuff on his site and I highly recommend it as a
source for finding out about interesting techniques. What he describes
is quite similar to the EOF link I put in one of my earlier posts.
> Y
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 curre
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 wi
> 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,
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
essage --------
> 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:
>
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 "r
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
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 e
>> >>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 pro
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 defini
> > 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 S
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.
Defin
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
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
17 matches
Mail list logo
