Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
pyodbc
Home
+ new post
About this group
Join this group
Message from discussion Getting a lot of errors with near-simultaneous AJAX statements (FreeTDS, UnixODBC, PyODBC, SQL Server 2008)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
ashaner  
View profile  
 More options May 3 2011, 10:09 am
From: ashaner <asha...@chumpland.org>
Date: Tue, 3 May 2011 07:09:03 -0700 (PDT)
Local: Tues, May 3 2011 10:09 am
Subject: Re: Getting a lot of errors with near-simultaneous AJAX statements (FreeTDS, UnixODBC, PyODBC, SQL Server 2008)
Print | View thread | Show original | Report this message | Find messages by this author
On May 3, 7:36 am, csudcy <csu...@gmail.com> wrote:
> SQL Server - 2005/2008 (results were identical)
> Ubuntu - 10.04.2 LTS
> FreeTDS - 0.82 (tried 0.91.dev.20110415RC2 but it was seg-faulting)
> UnixODBC - 2.2.11-21
> PyODBC - 2.1.8
> Django PyODBC - ? (see below)
> Django - 1.3.0
> uWSGI - 0.9.7.2
> Nginx - 0.8.54

All of my django apps use nginx / apache / mod_wsgi / psycopg2 /
postgresql, so I'm unfamiliar with Django PyODBC and uWSGI. However I
do have some cherrypy apps that use pyodbc to connect to Sql Server
2008. From recollection, unixodbc 2.2.x and freetds 0.82 had no issues
for me. But if you are going to try newer versions of freetds (0.83
and higher), then definitely try to use unixodbc 2.3.0 as well.

> The SQL errors only get printed to the uWSGI shell at the moment so
> Ive lost them from my extensive testing before. So, Ive just done some
> more testing (using the js console way) and the results are:
> ~53%: pyodbc.Error: ('08S01', '[08S01] [FreeTDS][SQL Server]Write to
> the server failed (20006) (SQLPrepare)')
> ~44%: pyodbc.Error: ('01000', '[01000] [FreeTDS][SQL Server]Unexpected
> EOF from the server (20017) (SQLPrepare)')
> ~3%: pyodbc.Error: ('HY000', 'The driver did not supply an error!')
> I also remember getting one about 'could not find prepared statement
> 0' before. I think they all happen pretty randomly.

I've never encountered the first two, but I've had the HY000 error
many times. At this point my only suggestion is to try the newer
unixodbc (2.3.0) with a newer freetds (>=0.83) just to compare. I also
distinctly remember getting segfaults on one of my servers while
messing around with different versions of these two packages.

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google