Re: [DB-SIG] [SQLObject] Re: SQLite connection - relative filename

2005-04-01 Thread Ian Bicking
Clark, Chris M wrote: def uri_parse(uri): module_name = uri.split(':', 1) . My 2 cents: for parsing the URI I like semi-colons ';' as separators, it is a little ODBC like but it has less collisions than colons do. This particular colon is for indicating the database type, like mysql:..., o

RE: [DB-SIG] [SQLObject] Re: SQLite connection - relative filename

2005-04-01 Thread Clark, Chris M
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ian Bicking > Sent: Friday, April 01, 2005 12:23 PM > To: Paul Moore > Cc: [EMAIL PROTECTED]; Python DB-SIG > Mailing List > Subject: [DB-SIG] [SQLObject] Re: SQLite connection - > relative filenam

[DB-SIG] [SQLObject] Re: SQLite connection - relative filename

2005-04-01 Thread Ian Bicking
Paul Moore wrote: Maybe _parseURI should use urllib.url2pathname? That would still be mildly suboptimal, as url2pathname doesn't accept the common form '///C:/a/b/...'. But that's a stdlib issue. Incidentally, while we're on the topic of URIs, I'd like to move all this URI parsing stuff into a lib

RE: [DB-SIG] URI syntax for databases

2005-04-01 Thread Dittmar, Daniel
>> An alternative would be to always use uri_connect. In >addition, a set of >> modules is provided that implements this uri translation for older >> drivers. The user would then have to choose between the real >module or >> the translation module. > >That seems awkward, but I suppose doable.