We had a similar problem here with our app that we built. A lot of sql
buried in the perl code that needed to be reworked every time the db
schema changed.
We changed our approach to objects. That way, your sql queries are in
the objects themselves and you call methods to trigger those sql
queries. Making the db creation and connection as part of an object in
itself helped out a lot as well.
Hope this helps you. Good luck,
Eric
On Thu, 2004-09-30 at 15:52, Sean Davis wrote:
> I am building a cgi::application that queries pretty extensively (at
> least for me) from a MySQL database. I am having trouble with
> maintainability, as the SQL code is mixed into the perl code and,
> unfortunately, we are changing the database schema fairly often right
> now. I was wondering what hints folks have about managing the SQL
> parts away from the logic of the code. For my limited programming
> skills, writing subroutines within my CGI::App is easiest but probably
> not the most flexible.
>
> Thanks,
> Sean
>
>
> ---------------------------------------------------------------------
> Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
> http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
> To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
> For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
>
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
