I didn't see anything in my testing that indicated there was any problem in
pymssql. My problems were limited, I think, to the code in dbMsSQL.py and
(what appeared to be) an inability of dCursorMixin to handle what we were
sending it.
Gary
Nate Lowrie wrote:
>
> On Tue, Apr 8, 2008 at 10:51 PM, johnf <[EMAIL PROTECTED]> wrote:
>> On Tuesday 08 April 2008 08:35:45 pm Gary_Krell wrote:
>> > getConnection changes the host name that it gets from the connectInfo
>> > object by appending the port, if one exists, or "1433" as a default,
>> if
>> > none is passed. As I understand it, specifying the port is not
>> necessary,
>> > at least in SS2005, unless you are running a non-default (named)
>> instance,
>> > OR running a default (un-named) instance on a non-standard port AND
>> not
>> > running MS SQL Server Browser. My instance is un-named, using the
>> default
>> > (1433) port. (The above code works whether the Browser is running or
>> > stopped.) The pymssql FAQ mentions handling named instances, but
>> dbMsSQL
>> > does not appear to allow for this case
>>
>> Using 5555 as a port worked on my 2003.
>> The very reason Carl and I added the port was because we were following
>> the
>> doc's
>>
>> Q: How to connect to non-default (named) instance?
>>
>> A: First, make sure that the SQL Server instance you're connecting to is
>> configured to listen on a static TCP port. It can be set on the server
>> using
>> Server Network Utility available in the Microsoft SQL Server start menu
>> group -- or in SQL Server Configuration Utility in case of SQL 2005.
>> The simplest method to connect to this instance is then to use:
>> conn = _mssql.connect('sqlhost:4801', 'user', 'password')
>> (the port number shown is an example)
>>
>> So it's suppose to work for 2005???
>>
>> I'm not sure removing it is a good idea, However, I wonder if we are
>> doing it
>> correctly. It looks like the connection is string is missing a colon?
>> I'm
>> guessing that it works for me because I'm on Linux (using FreeTDS) and
>> my
>> standard windows connection uses 1433. I can't recall at the moment
>> what
>> testing was done. But I think it was working on windows.
>>
>> Bottom line: The guy that created the psmssql moldule is no longer
>> actively
>> supporting the module. Maybe, we should look for a replacement???? As
>> Gary
>> is not the only person that has trouble getting it to work. But I know
>> Nate
>> is using it on some web projects and it works for him.
>
> The port call in the host name works for me for 2003. I am connecting
> on 1733 I think... Bottom line is that pymssl is working for me,
> though I don't use it in a dabo context.
>
> Nate L.
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
