On Tue, Nov 30, 2004 at 12:33:40AM +0100, Hans Schou wrote:
> On Mon, 29 Nov 2004, Darren Duncan wrote:
>
> > On Mon, 29 Nov 2004, Hans Schou wrote:
> > > But making dbi:// a default prefix will probably restrict the use of
> > > DBURL to only DBI. It is not realistic to think that MySQL and
> > > PostgreSQL would implement such a naming scheme, where as the original
> > > idea might be accepted.
> >
> > Considering that it sounds like you want to embed your DBURL
> > implementation into the DBI interface spec itself, then why is
> > DBI-specificity a problem?
>
> I wanted the syntax to be short. An example:
> $dbh = DBI->connect("dburl=dbi://localhost/pgsql");
> $dbh = DBI->connect("dburl=pgsql://localhost");
>
> I can see no reason for having dbi:// as DBI would know that a URL
> will always follow a dburl=
>
> If the implementation in DBI would have the syntax:
> $dbh = DBI->connect("dbi://localhost/pgsql");
> I could see a reason. But this will only consider DBI, not PostgreSQL,
> MySQL or Oracle.
"dbi" doesn't have to mean the Perl DBI.
If you're trying to create a wider standard with support in vendor
tools then best to come back when there's wider support and some
implementations existing.
Alternatively write a DBI subclass to do-the-right-thing.
Tim.
