>> >>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 in a lot of
>environments.
>Remember that a large number of people in the mod_perl world
>can't use 'em
>because they (we) use MySQL. If one wanted to emulate this
>behavior with
>MySQL, you would essentially clone the functionality of your stored
>procedures using Perl + DBI inside your persistence layer. That is a
>perfectly viable approach too, but a lot less efficient than stored
>procedures (many roundtrips versus one).
Interesting, I will be working w/MySQL in a few days on a
side project of my own. We'll see how my outlook changes ;)
Any recommendations?
Regards,
Dave
"Language shapes the way we think, and determines what we can
think about." -- B. L. Whorf
