Two steps forward and one step back
Like many things in life, our latest version of the MyLibrary modules are an example of two steps forward and one step back.
Rob spent good time refactoring some of the underlying database code in Facets.pm, Terms.pm, etc. Through this good work he was able to significantly speed up the creation and display of MyLibrary resource objects. Cool. As I packaged up his improvements and tested them against my various applications I noticed things had broken. More specifically, the make install process over wrote my previously created Config.pm module containing the specifications of all my MyLibrary instances. Running my applications I got errors like this:
Can’t connect to data source , no database driver specified and DBI_DSN env var not set at /usr/lib/perl5/site_perl/5.8.8/MyLibrary/DB.pm line 42
After using the config_mylibrary.pl utility I was able to restore my instances, but this not what developers will want to do. We need to figure out how to retain MyLibrary instance configurations when installing new versions of the modules. Hmmm…
Back to the installation drawing board.
3 Responses to “Two steps forward and one step back”
Discussion Area - Leave a Comment
You must be logged in to post a comment.
Well, I don’t see this as a problem. Configurations should not not sit in system folders anyway. Even if MyLibrary offers that as a convenience (and I am taking advantage of it right now without much shame
) , I’ll move the database connection data to separate config files after the prototyping is over.
Is the new code public ?
Yes, the source code is available even if it is not on CPAN; it is in a CVS repository. See:
As of right now the CVS repository may not be accessible off-campus, but by the time anybody reads this it probably will be.
As soon as the new CVS repository is available, I will create a post to the blog with the connection information. The source code is available from CPAN, though. If folks would like to contribute to the repository, please let us know.