On Mon, Oct 04, 2004 at 02:36:47AM +0000, Mark Stosberg wrote: > > I think this is the cleanest way to implement database access in > > CGI::App, and I would think that Class::DBI falls into this category as > > well. > > I agree here.
Good, that's where I was thinking CDBI fit into your model as well. > > Of the dependancies you list, I believe only configuration data should > > be shared between your CGIApp modules and your database modules. And > > that can be handled by sharing the same configuration files (I usually > > just use a perl module that defines all the variables that are needed > > and 'use' it in all my modules). FWIW, I am using the plugin that you wrote (C::A::P::ConfigAuto) for reading in my configuration file into my CGI::App module and am using the Config::Auto module for parsing the same file from the Class::DBI module to get database handle details. It's working great. > So it sounds like you advocate using Ima::DBI, the solution that > Class::DBI uses? I can't speak for Cees but as a CDBI user, I rarely think about Ima::DBI. Occasionally I'll check some syntax for an inherited command such as set_sql. Although I'm not intimately familiar with the Ima::DBI/CDBI codebase, I can't imagine that Ima::DBI on its own would be as useful as the CDBI module. William -- Knowmad Services Inc. http://www.knowmad.com --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
