OK, itll go into the 0.2 series since id rather not be supporting multiple syntaxes (i.e. the old one is going to go)

On Apr 17, 2006, at 1:49 AM, William K. Volkman wrote:

On Mon, 2006-04-17 at 01:23 -0400, Michael Bayer wrote:
On Apr 17, 2006, at 12:42 AM, William K. Volkman wrote:

Hello,

I just getting started evaluating SQL Alchemy.

Not recalling the documentation very clearly I wrote the DB URL
as I expected it to work:

engine = create_engine('postgres://scott:[EMAIL PROTECTED]:5049/test')


if you can find me a full specification for this syntax, I will
implement it (or of course if someone contributes).  otherwise I find
it pretty arbitrary and non-standard, and the only reason people seem
to know it is because theyve used SQLObject before (or perhaps PHP's
Pear::DB.  does anything else use it?).

Humm... http://www.w3.org/Addressing/ is a good place to start.

Of course it is high level and not DB specific however if
you pull up the Uniform Resource Locators (URL) RFC.
http://www.rfc-editor.org/rfc/rfc1738.txt
you will find that "mailto" and "news" are the only
common exception to the canonical form:

3.1. Common Internet Scheme Syntax

   While the syntax for the rest of the URL may vary depending on the
   particular scheme selected, URL schemes that involve the direct use
   of an IP-based protocol to a specified host on the Internet use a
   common syntax for the scheme-specific data:

        //<user>:<password>@<host>:<port>/<url-path>

   Some or all of the parts "<user>:<password>@", ":<password>",
   ":<port>", and "/<url-path>" may be excluded.  The scheme specific
data start with a double slash "//" to indicate that it complies with the common Internet scheme syntax. The different components obey the
   following rules:

    user
        An optional user name. Some schemes (e.g., ftp) allow the
        specification of a user name.

    password
        An optional password. If present, it follows the user
        name separated from it by a colon.

   The user name (and password), if present, are followed by a
commercial at-sign "@". Within the user and password field, any ":",
   "@", or "/" must be encoded.

A common mistake is to forget that the host name portion is not
optional so the URL for SQlite files is: "sqlite:///mydb" and
not "sqlite://mydb", if they really wanted to just be scheme
specific then "sqlite:mydb" or "sqllite::memory:" would also
be correct.

HTH,
William.



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel? cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users

Reply via email to