I see,
I have back ported the freetds package from unstable and it seems to
work fine for me.
So in order to make everybody happy we would have to make it backwards
compatible
with previous versions of python and previous versions of freetds(the
version in sarge is quite old).
It seems like to much of hassle to make everybody happy, i guess we
just keep rocking with our homemade patches.
Maybe for the next release we just make sure we don't suddenly require
python 2.5/6 and newer freeteds. So that things can stabilize
somewhat.
On 9/12/05, Laura Vetter <Lau...@es...> wrote:
> Jakub,
>
> We are also using debian but our problem isn't with python 2.4, it becaus=
e debian stable uses an old version of freetds and we were unable to get th=
e newer version, which is required for python 2.4, to compile with other re=
quired dependencies on debian. So it looks like some code in freetds needs=
to be ported to debian so it can compile. Or perhaps we could find out wh=
y the new version of pymssql requires the new version of freetds and see if=
it would make sense to take out that requirement.
>
> Laura.
>
> -----Original Message-----
> From: Jakub Labath [mailto:jl...@gm...]
> Sent: Monday, September 12, 2005 10:57 AM
> To: Laura Vetter
> Subject: Re: [Pymssql-users] patch pymssql.py - Permits database queries
> that return no recordsets
>
>
> Hi Laura,
>
> I believe this is the same problem I had and I also provided a fix for
> it, and Andrzej already added it to current version.
>
> I do have a question, and I am wondering what do you guys think?
> I myself am using python 2.3 and I know that Andrzej is developing for
> python 2.4 and the same as Laura the current version simply won't
> compile for me.
>
> Is there any value in putting some time and effort to make the pymssql
> backwards compatible with previous versions of python.
>
> And if so how far back should we go? Python 2.3. Python 2.2?
>
> I know we should just all be using Python 2.4, but 2.3 is standard on
> debian (which I use). And also on some other systems (OS X Jaguar).
>
> Andrzej, I wouldn't mind helping with this effort since it is in my
> best interest :-).
>
> Your thoughts?
>
>
>
> Best Regards
>
> On 9/12/05, Laura Vetter <Lau...@es...> wrote:
> > Problem: I want to execute queries that change the schema of a databas=
e and I would prefer that those queries not return any recordsets.
> >
> > Fix: Made it so code looks to see if there are recordsets before going =
into the recordset array and reading from it.
> >
> > Note: Please note that I am using version 0.7.1 because I couldn't inst=
all the latest version because my system was have problems compiling and in=
stalling the dependancies for the latest version.
> >
> > My apologies in advance if you don't want the diff attached. I tried t=
o check the archives to see how to send it but the archives are either non-=
existant or having problems. Also, I'm relatively new to python, so please=
be kind.
> >
> > <<pymssql.py.diff>>
> >
> > Laura Vetter
> >
> >
> >
> >
>
>
|
