Re: DBIx::DBH - Perl extension for simplifying database connections

2004-12-07 Thread Matthew Persico
On Mon, 6 Dec 2004 17:23:46 +, Martyn J. Pearce [EMAIL PROTECTED] wrote: On Fri, Dec 03, 2004 at 11:25:53AM +, Tim Bunce wrote: Yes. It's finely balanced though. I can see merit on both sides. The fill in a form situation is relatively common. But beyond the MySQL/Pg model of

RE: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Orton, Yves
Henrik Tougaard wrote on 07 December 2004 10:59 Martyn J. Pearce skrev: On Fri, Dec 03, 2004 at 11:25:53AM +, Tim Bunce wrote: ... The simplest fix is to standardize one set of driver DSN attribute names so that at least the host, port, and database (schema) can be specified in a

RE: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Christopher Hicks
On Tue, 7 Dec 2004, Henrik Tougaard wrote: Maybe the number of responses on this thread come from people who have this itch to scratch. Huh? I've only been seeing what got cross-posted on this to module-authors until today, but I just subscribed to dbi-usres n I have heard Tim Bunce (DBI,

RE: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Orton, Yves
Christopher Hicks wrote: Coming up with common set of parameters that most DB's are going to require and then providing standardized names for them would seem to be useful in general. So far I havent seen anyone provide something that a given driver Has To Have that doesn't fit into the

RE: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Christopher Hicks
On Tue, 7 Dec 2004, Orton, Yves wrote: I was given the Henrik or some other hypothetical respondant the benefit of the doubt. I figured that out by the end of reading your email. :-) :-] I thought it was clear I think that this is both doable and worth doing. Yes yes. I didn't think there was

Re: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Sam Vilain
Orton, Yves wrote: DBD::Ingres does something similar. DBD::Oracle appears to be closer to Sybase/MySQl: dbi:Oracle:host=myhost.com;sid=ORCL Normally you don't bother with connection parameters with Oracle at all: DBI-connect(dbi:Oracle:, database, password); Instead, you configure which logical

Re: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread John Siracusa
On Wed, 08 Dec 2004 10:21:35 +1300, Sam Vilain [EMAIL PROTECTED] wrote: I think that this information should be removed from most programs altogether. They should just have to specify a logical data source (possibly including a schema version), then a module with a config file maps that to a

Re: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Tim Bunce
On Tue, Dec 07, 2004 at 11:51:41AM -0600, Chris Josephes wrote: Either way, does this traffic need to be replicated on both dbi-users and module-authors?? I would think the DBI list would supercede the other. I agree. Can anyone replying to this thread please remove [EMAIL PROTECTED] from

Re: DBIx::DBH - Perl extension for simplifying database connections

2004-12-07 Thread Mark Stosberg
On Tue, Dec 07, 2004 at 12:38:12PM +, Tim Bunce wrote: --- The simplest fix is to standardize one set of driver DSN attribute names so that at least the host, port, and database (schema) can be specified in a portable way. Most drivers already support the foo=bar;... style in the DSN

RE: DBIx::DBH - Perl extension for simplifying database connectio ns

2004-12-07 Thread Chris Josephes
On Tue, 7 Dec 2004, Christopher Hicks wrote: I don't care about Oracle or any of the rest. Making this work with PG and MySQL will solve 90% of the world's problems. I don't see why it couldn't be extended to include whatever parameters where necessary for any of the proprietary databases,