DBIx:: is appropriate. DBI:: is not. It seems like you should use SQL:: if you just work with abstract SQL statements (which the user then passes to their database or uses in some other way), and DBIx:: if you'll actually be talking to DBI/DBD underneath for the user.
You may want to join the poop-group: http://poop.sourceforge.net/ for the overview and http://lists.sourceforge.net/lists/listinfo/poop-group for the discussion list. The poop-group list may be more appropriate than the dbi-dev list for this sort of thing. (Ironically, most of the interesting poop projects are badly named: Alzabo, Tangram, SPOPS, BingoX::Carbon, etc.) On Sun, Oct 21, 2001 at 03:12:01PM -0700, Jason W May wrote: > I'm working on a module that I hope will provide a similar function for SQL > code that the various templating modules provide for HTML generation. > > The goal is to move SQL code entirely out of the Perl, and to provide a very > straightforward means of executing the SQL statements that are maintained in > separate files. > > e.g. given this SQL statement in a file named "lookup_employee": > > select name, > salary, > hire_date > from EMPLOYEE > where id = :id > > The module works like this: > > my $thingy = new Thingy; > my $data = { id => 473 }; > $thingy->execute("lookup_employee", $data); > print "Employee $data->{id} is $data->{name} with salary $data->{salary}\n"; > > > What is an appropriate module name for this package? I'm unclear on the > rules regarding use of the various db-related namespaces on CPAN. > > Some ideas: > DBIx::Template > DBI::Template > SQL::Template > DBIx::SQLManager > > Suggestions welcome, > -Jason > -- _ivan
