I have a webapplication server that worked this way and it was a good solution to me. I used .sql scripts and alter the tables on the fly. Webparts changed with Apache::Reload. If you prefer the use of fetchrow_hashref your application did not notice most changes in the database anyway. That saved most time for me.
Boris

In reply to Re: OT: Ways of managing changes to a database's structure during a project. by borisz
in thread OT: Ways of managing changes to a database's structure during a project. by EvdB

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":