Closed GoogleCodeExporter closed 9 years ago
unixODBC config
odbc_config --version --libs --static-libs --libtool-libs --longodbcversion
--header --ulen
2.3.0
-L/usr/local/lib -lodbc
/usr/local/lib/libodbc.a
/usr/local/lib/libodbc.la
3.52
#ifndef HAVE_UNISTD_H
#define HAVE_UNISTD_H
#endif
#ifndef HAVE_PWD_H
#define HAVE_PWD_H
#endif
#ifndef HAVE_SYS_TYPES_H
#define HAVE_SYS_TYPES_H
#endif
#ifndef HAVE_LONG_LONG
#define HAVE_LONG_LONG
#endif
#ifndef ODBCINT64
#define ODBCINT64 long long
#endif
#ifndef UODBCINT64
#define UODBCINT64 unsigned long long
#endif
#ifndef SIZEOF_LONG_INT
#define SIZEOF_LONG_INT 4
#endif
-DSIZEOF_SQLULEN=4
Original comment by victor.o...@gmail.com
on 20 Jan 2012 at 6:05
In the fisql tool the query definitely works correctly even on 3072 characters.
Original comment by victor.o...@gmail.com
on 20 Jan 2012 at 6:11
Has anyone figured out a way around this problem until it is fixed?
Original comment by wpu.cl...@gmail.com
on 11 Apr 2012 at 12:23
Is there still no fix or workaround?
Original comment by AlwaysCa...@googlemail.com
on 13 May 2012 at 6:51
Casting to ntext is possible workaround.
It solves problem for me.
Original comment by Ponimas...@gmail.com
on 14 May 2012 at 7:08
Worked for me too, thank you. A fix still would be good, I barely can use this
Workaround in production.
Anyway, thanks a lot.
Original comment by AlwaysCa...@googlemail.com
on 14 May 2012 at 10:25
We are fetching a text field from a system table in Vertica and so there is no
way we can alter that table. Can anyone please provide a solution/fix to this
issue?
Original comment by katti.sh...@gmail.com
on 1 Jun 2012 at 2:39
I have also been having this same 'python: realloc(): invalid pointer' problem
with pyodbc 3.0.3 and lengthy text fields. I reverted to pyodbc 2.1.11 and
everything seems to be working fine.
Original comment by br...@huron-data.com
on 14 Jun 2012 at 4:39
This may have been fixed in 3.0.6-beta07
(66c51365b2a2283a0742ca9cab771f3362a9fbb8).
Reading ASCII fields somewhere around 4K and up were failing with a realloc
error.
Can you retest with this version?
Original comment by mkleehammer
on 23 Jun 2012 at 11:17
Finally got around to looking at this, and I just upgraded my version to 3.0.6
(not beta), and it seems to have fixed the issue. Just ran a bunch of tests and
nothing else appears to have been affected.
Thanks!
Original comment by wpu.cl...@gmail.com
on 13 Jul 2012 at 3:41
Great. Looking at the source code, it seems hard for me to tell exactly what
fixed it. Also, the release note on the home page doesn't mention this issue
being fixed. It would be great if the author of the this release can point out
the issue was fixed and exactly what fixed it!
Thanks pyodbc developers
Original comment by katti.sh...@gmail.com
on 13 Jul 2012 at 4:07
Original comment by mkleehammer
on 27 Sep 2012 at 10:19
Today, I find same problem. GetData, the sql column buffer length > 12000 char,
SQLGetData func, return cbData is -4...
I modify getdata.cpp:311, char tempBuffer[1026]
to:
char tempBuffer[40260];
one fetch ok...
build and install .
Original comment by superstr...@gmail.com
on 2 Sep 2013 at 4:46
Original issue reported on code.google.com by
victor.o...@gmail.com
on 20 Jan 2012 at 5:59