Re: [SQLObject] possible bug in pymssql make_conn_str

[Oleg B. <ph...@ph...>]

Hi! Please avoid top-posting. You know the problem:

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

   My answer is below.

On Fri, Aug 16, 2013 at 11:19:35AM -0700, Robert Ayrapetyan <rob...@gm...> wrote:
> Not getting own emails and replies (all mailing list settings are set 
> by default,
> however I found a reply in a mail archive here:
> http://sourceforge.net/mailarchive/forum.php?forum_name=sqlobject-discuss&max_rows=25&style=nested&viewmonth=201308).
> 
> Anyway, instead of
> 
> [".", keys.user, keys.password, keys.db, 0, 60, None, False, keys.host, 
> None, keys.port]
> 
> for
> 
> def connect(server='.', user='', password='', database='', timeout=0,
>           login_timeout=60, charset=None, as_dict=False,
>           host='', appname=None, port='1433')
> 
> (which works fine for me)
> 
> it would be better to pass only user, password, database, host and port 
> (if set explicitly)
> (leaving default vals for other params).
> I'm not a python guru and have no idea how to implement this via 
> dynamically generated list of params (similarly to how it was).

   I changed the generation of parameters for pymssql. Committed in the
revisions 4644, 4645 in branch 1.5 (code and news), 4646 in the trunk.
   Can you test the patch? Or do you want me to roll out a beta release?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.