On Tue, 26 Feb 2002, Mark Fowler wrote:
> On Tue, 26 Feb 2002, Aaron J Mackey wrote: > > > 1. We need to specify connection metadata (DBD driver to use, and > > connection parameters: we can specify those at import time (use Inline SQL > > => DATA, HOST => 'myhost', etc), or at run time via Inline->bind(), or in > > a metadata section of the __DATA__ stream (not sure I like that so much). > > When you say "import time" bear in mind that as it stands the stuff you > mention in "use Inline SQL => DATA, HOST => 'myhost', etc" is inaccessible > to the run time code, only the compiling to cache code, meaning that this > meta data will remain the same until you edit the file or delete the > .Inline Yeah I guess this is where Inline::SQL might differ (perhaps this really should be a DBIx::Inline module instead), since there's not really any compilation going on; we need to connect to the database anew on every invocation, so there's no reason we can't accept new values (perhaps unchanged, perhaps not) every time; there's no time saved by caching away only the "first" values that were ever used. To be honest, I can't see any reason why Inline::SQL would need much of any of the functionality Inline provides ;) (hence my DBIx::Inline alternative naming scheme). the "binding" is really just installing some coderef's into the caller's namespace that will be handled via a Inline::SQL-intermediated DBI session ... now of course I could write Inline::SQL using Inline::C to make it faster, but that's a different topic ;) -Aaron -- Aaron J Mackey Pearson Laboratory University of Virginia (434) 924-2821 [EMAIL PROTECTED]
