To me the value of database urls would be compatibility with other implementations of this obvious idea. Some examples I found by quick googling:
http://docs.sqlalchemy.org/en/rel_0_9/core/engines.html#database-urls http://docs.stackato.com/3.0/user/services/data-services.html#database-url https://github.com/kennethreitz/dj-database-url https://github.com/glenngillen/rails-database-url http://www.jguru.com/faq/view.jsp?EID=690 http://www.postgresql.org/docs/9.3/static/libpq-connect.html#LIBPQ-CONNSTRING It would be useful for somebody to survey these and then provide a perl module that's compatible with the consensus among these. It would also be a good place to document what the state of database urls currently is. --Gisle On Tue, Nov 26, 2013 at 9:42 AM, Tim Bunce <tim.bu...@pobox.com> wrote: > On Fri, Nov 22, 2013 at 05:13:53PM -0800, David E. Wheeler wrote: > > DBI Folks & Gisle, > > > > I want to add support for specifying database connections as URIs to > Sqitch, my DB change management system. I started working on it today, > following the examples of JDBC and PostgreSQL. Before I release, though, > I’d like a bit of feedback on a couple of things. > > > > First, I'm using the database name as the scheme in the URL. Some > examples: > > > > postgresql://user@localhost:5433/dbname > > sqlite:///path/to/foo.db > > > > This is to make it easy to tell one DB from another. But I'm wondering > if I should follow the example of JDBC more closely, and prepend "db:" or > something to them. More like DBI DSNs, too. However, it would require a bit > more work, as URI.pm does not currently recognize multiple colon-delimited > strings as scheme names AFAICT. :-( > > Why not define a direct translation from a URL to a DBI DSN? > A translation that doesn't require knowledge of any driver-specifics. > > Tim. >
