Menu
▾
▴
python-sybase-misc
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
(3) |
Apr
(26) |
May
(7) |
Jun
|
Jul
(12) |
Aug
|
Sep
(13) |
Oct
(6) |
Nov
(14) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(31) |
Feb
(15) |
Mar
(6) |
Apr
(18) |
May
(11) |
Jun
(3) |
Jul
(7) |
Aug
(5) |
Sep
(6) |
Oct
(1) |
Nov
(2) |
Dec
(6) |
| 2004 |
Jan
(3) |
Feb
(3) |
Mar
(18) |
Apr
(4) |
May
(13) |
Jun
(32) |
Jul
(21) |
Aug
(22) |
Sep
(11) |
Oct
(2) |
Nov
(6) |
Dec
(5) |
| 2005 |
Jan
(4) |
Feb
(16) |
Mar
(21) |
Apr
(10) |
May
(1) |
Jun
(5) |
Jul
(3) |
Aug
(3) |
Sep
(13) |
Oct
(15) |
Nov
(20) |
Dec
|
| 2006 |
Jan
(3) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
(4) |
Jun
(6) |
Jul
(23) |
Aug
(6) |
Sep
(5) |
Oct
(8) |
Nov
|
Dec
(12) |
| 2007 |
Jan
(2) |
Feb
(5) |
Mar
|
Apr
|
May
(9) |
Jun
(1) |
Jul
(6) |
Aug
(5) |
Sep
(3) |
Oct
|
Nov
(5) |
Dec
(6) |
| 2008 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(3) |
May
|
Jun
(12) |
Jul
|
Aug
(1) |
Sep
|
Oct
(7) |
Nov
(1) |
Dec
(4) |
| 2009 |
Jan
|
Feb
(2) |
Mar
(16) |
Apr
|
May
|
Jun
|
Jul
(5) |
Aug
(21) |
Sep
(11) |
Oct
(4) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
| 2011 |
Jan
(9) |
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(1) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <msa...@gr...> - 2004-04-07 02:57:24
|
I am recieving this error
DatabaseError: Msg 8153, State 1, Line 1
Warning: Null value is eliminated by an aggregate or other SET operation.
which should be a warning
What is the recommended way to deal with this. If there is nothing
preset, I believe there should be a connection-level list of errors to
silently ignore (as in Subase.py:159)
def _servermsg_cb(ctx, conn, msg):
# This is what should be configurable
if msg.msgnumber not in (5701, 5703):
raise DatabaseError(_fmt_server(msg))
¿Shouldn't I get a severity level for this warning?
Thanks
Marcos
|
|
From: <Sha...@su...> - 2004-03-30 02:10:32
|
The only help I can give you is to say that I've seen it too (with
Python 2.2).
It flies in such a spectacular way, that there's no debug information,
nothing for the developers to chew on.=20
I "solved" it by downgrading to 0.35.
-----Original Message-----
From: pyt...@ww...
[mailto:pyt...@ww...] On Behalf Of
MK...@ub...
Sent: Wednesday, March 24, 2004 16:18
To: Pyt...@ww...
Subject: [python-sybase] error using Python Sybase
I installed Python-sybase 0.36 for python 2.3.3=20
The O.S is Windows2000=20
The database is Sybase 12.0=20
and using IDLE 1.0.2 I typed :=20
>>>import Sybase=20
>>>db=3DSybase.connect('SERVDBDEV','def33','CFSTat')=20
And there's a Pythonw error : "the instruction at 0x009dd8a7 referenced
memory at (0x00000001) the memory could not be written.=20
Can Any One Help me=20
Thanks
---
Confidentiality Notice: This email transmission may contain confidential =
or legally privileged information that is intended only for the =
individual or entity named in the e-mail address. If you are not the =
intended recipient, you are hereby notified that any disclosure, =
copying, distribution, or reliance upon the contents of this e-mail is =
strictly prohibited. If you have received this e-mail transmission in =
error, please reply to the sender, so that arrangements can be made for =
proper delivery, and then please delete the message from your inbox.
|
|
From: <MK...@ub...> - 2004-03-25 09:03:04
|
I installed Python-sybase 0.36 for python 2.3.3
The O.S is Windows2000
The database is Sybase 12.0
and using IDLE 1.0.2 I typed :
>>>import Sybase
>>>db=Sybase.connect('SERVDBDEV','def33','CFSTat')
And there's a Pythonw error : "the instruction at 0x009dd8a7 referenced
memory at (0x00000001) the memory could not be written.
Can Any One Help me
Thanks |
|
From: Brian B. <bb...@pa...> - 2004-03-17 09:41:30
|
Thanks Dave - that fixed it. -----Original Message----- From: pyt...@ww... [mailto:pyt...@ww...]On Behalf Of Dave Cole Sent: Monday, March 15, 2004 11:42 PM To: pyt...@ww... Subject: RE: [python-sybase] Python sybase-0.36 module with RedHat 9 On Tue, 2004-03-16 at 15:04, Brian Beaver wrote: > Full output below, with the ldd following...thanks > > # python setup.py build_ext [snip] > gcc -shared build/temp.linux-i686-2.2/blk.o > build/temp.linux-i686-2.2/databuf.o build/temp.linux-i686-2.2/cmd.o > build/temp.linux-i686-2.2/conn.o build/temp.linux-i686-2.2/ctx.o > build/temp.linux-i686-2.2/datafmt.o build/temp.linux-i686-2.2/iodesc.o > build/temp.linux-i686-2.2/locale.o build/temp.linux-i686-2.2/msgs.o > build/temp.linux-i686-2.2/numeric.o build/temp.linux-i686-2.2/money.o > build/temp.linux-i686-2.2/datetime.o build/temp.linux-i686-2.2/sybasect.o > -L/opt/sybase-12.5/OCS/lib -o build/lib.linux-i686-2.2/sybasect.so Just as I suspected - it is not finding the Sybase libraries. Can you please try the attached patch to setup.py? - Dave -- http://www.object-craft.com.au |
|
From: Dave C. <dj...@ob...> - 2004-03-16 23:42:26
|
On Tue, 2004-03-16 at 15:04, Brian Beaver wrote: > Full output below, with the ldd following...thanks > > # python setup.py build_ext [snip] > gcc -shared build/temp.linux-i686-2.2/blk.o > build/temp.linux-i686-2.2/databuf.o build/temp.linux-i686-2.2/cmd.o > build/temp.linux-i686-2.2/conn.o build/temp.linux-i686-2.2/ctx.o > build/temp.linux-i686-2.2/datafmt.o build/temp.linux-i686-2.2/iodesc.o > build/temp.linux-i686-2.2/locale.o build/temp.linux-i686-2.2/msgs.o > build/temp.linux-i686-2.2/numeric.o build/temp.linux-i686-2.2/money.o > build/temp.linux-i686-2.2/datetime.o build/temp.linux-i686-2.2/sybasect.o > -L/opt/sybase-12.5/OCS/lib -o build/lib.linux-i686-2.2/sybasect.so Just as I suspected - it is not finding the Sybase libraries. Can you please try the attached patch to setup.py? - Dave -- http://www.object-craft.com.au |
|
From: Brian B. <bb...@pa...> - 2004-03-16 23:07:47
|
Full output below, with the ldd following...thanks
# python setup.py build_ext
running build_ext
building 'sybasect' extension
creating build/temp.linux-i686-2.2
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c blk.c -o build/temp.linux-i686-2.2/blk.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c databuf.c -o build/temp.linux-i686-2.2/databuf.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c cmd.c -o build/temp.linux-i686-2.2/cmd.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c conn.c -o build/temp.linux-i686-2.2/conn.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c ctx.c -o build/temp.linux-i686-2.2/ctx.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c datafmt.c -o build/temp.linux-i686-2.2/datafmt.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c iodesc.c -o build/temp.linux-i686-2.2/iodesc.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c locale.c -o build/temp.linux-i686-2.2/locale.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c msgs.c -o build/temp.linux-i686-2.2/msgs.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c numeric.c -o build/temp.linux-i686-2.2/numeric.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c money.c -o build/temp.linux-i686-2.2/money.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c datetime.c -o
build/temp.linux-i686-2.2/datetime.o
gcc -DNDEBUG -O2 -g -pipe -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -fPIC
-DWANT_BULKCOPY -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
-DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
-DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM
-DHAVE_CS_CALC -DHAVE_CS_CMP -I/opt/sybase-12.5/OCS/include
-I/usr/include/python2.2 -c sybasect.c -o
build/temp.linux-i686-2.2/sybasect.o
creating build/lib.linux-i686-2.2
gcc -shared build/temp.linux-i686-2.2/blk.o
build/temp.linux-i686-2.2/databuf.o build/temp.linux-i686-2.2/cmd.o
build/temp.linux-i686-2.2/conn.o build/temp.linux-i686-2.2/ctx.o
build/temp.linux-i686-2.2/datafmt.o build/temp.linux-i686-2.2/iodesc.o
build/temp.linux-i686-2.2/locale.o build/temp.linux-i686-2.2/msgs.o
build/temp.linux-i686-2.2/numeric.o build/temp.linux-i686-2.2/money.o
build/temp.linux-i686-2.2/datetime.o build/temp.linux-i686-2.2/sybasect.o
-L/opt/sybase-12.5/OCS/lib -o build/lib.linux-i686-2.2/sybasect.so
# ldd build/lib.linux-i686-2.2/sybasect.so
libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
-----Original Message-----
From: pyt...@ww...
To: pyt...@ob...
Sent: 3/15/2004 10:20 PM
Subject: RE: [python-sybase] Python sybase-0.36 module with RedHat 9
On Tue, 2004-03-16 at 13:07, Brian Beaver wrote:
> Thanks for the quick reply - here's the ldd info
>
> # ldd /usr/lib/python2.2/site-packages/sybasect.so
> libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
That does not look right - there is no reference to the Sybase
libraries. Can you capture and post the output from
$ python setup.py build_ext
Looks like it is not linking against the Sybase libraries at all.
- Dave
--
http://www.object-craft.com.au
_______________________________________________
Python-sybase mailing list
Pyt...@ww...
https://www.object-craft.com.au/cgi-bin/mailman/listinfo/python-sybase
|
|
From: Dave C. <dj...@ob...> - 2004-03-16 22:20:53
|
On Tue, 2004-03-16 at 13:07, Brian Beaver wrote: > Thanks for the quick reply - here's the ldd info > > # ldd /usr/lib/python2.2/site-packages/sybasect.so > libc.so.6 => /lib/tls/libc.so.6 (0x42000000) > /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) That does not look right - there is no reference to the Sybase libraries. Can you capture and post the output from $ python setup.py build_ext Looks like it is not linking against the Sybase libraries at all. - Dave -- http://www.object-craft.com.au |
|
From: Brian B. <bb...@pa...> - 2004-03-16 21:10:03
|
Thanks for the quick reply - here's the ldd info
# ldd /usr/lib/python2.2/site-packages/sybasect.so
libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
-----Original Message-----
From: pyt...@ww...
To: 'pyt...@ww...'
Sent: 3/15/2004 6:11 PM
Subject: Re: [python-sybase] Python sybase-0.36 module with RedHat 9
On Tue, 2004-03-16 at 09:23, Brian Beaver wrote:
> Installed Redhat 9, sybase12.5, sybase-0.36 python module. Source the
> Sybase .profile to set all env vars correctly, but get undefined
symbol
> error below.
>
> >>> import Sybase
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "/usr/lib/python2.2/site-packages/Sybase.py", line 20, in ?
> from sybasect import *
> ImportError: /usr/lib/python2.2/site-packages/sybasect.so: undefined
symbol:
> cs_dt_info
> >>>
>
> # echo $LD_LIBRARY_PATH
>
/opt/sybase-12.5/ASE/lib:/opt/sybase-12.5/FTS/lib:/opt/sybase-12.5/OCS/l
ib:/
> opt/sybase-12.5/SQLRemote/lib:/opt/sybase-12.5/lib
>
> Any ideas?
Try doing this:
$ ldd /usr/lib/python2.2/site-packages/sybasect.so
- Dave
--
http://www.object-craft.com.au
_______________________________________________
Python-sybase mailing list
Pyt...@ww...
https://www.object-craft.com.au/cgi-bin/mailman/listinfo/python-sybase
|
|
From: Dave C. <dj...@ob...> - 2004-03-16 18:11:48
|
On Tue, 2004-03-16 at 09:23, Brian Beaver wrote: > Installed Redhat 9, sybase12.5, sybase-0.36 python module. Source the > Sybase .profile to set all env vars correctly, but get undefined symbol > error below. > > >>> import Sybase > Traceback (most recent call last): > File "<stdin>", line 1, in ? > File "/usr/lib/python2.2/site-packages/Sybase.py", line 20, in ? > from sybasect import * > ImportError: /usr/lib/python2.2/site-packages/sybasect.so: undefined symbol: > cs_dt_info > >>> > > # echo $LD_LIBRARY_PATH > /opt/sybase-12.5/ASE/lib:/opt/sybase-12.5/FTS/lib:/opt/sybase-12.5/OCS/lib:/ > opt/sybase-12.5/SQLRemote/lib:/opt/sybase-12.5/lib > > Any ideas? Try doing this: $ ldd /usr/lib/python2.2/site-packages/sybasect.so - Dave -- http://www.object-craft.com.au |
|
From: Brian B. <bb...@pa...> - 2004-03-16 17:26:10
|
Installed Redhat 9, sybase12.5, sybase-0.36 python module. Source the
Sybase .profile to set all env vars correctly, but get undefined symbol
error below.
>>> import Sybase
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.2/site-packages/Sybase.py", line 20, in ?
from sybasect import *
ImportError: /usr/lib/python2.2/site-packages/sybasect.so: undefined symbol:
cs_dt_info
>>>
# echo $LD_LIBRARY_PATH
/opt/sybase-12.5/ASE/lib:/opt/sybase-12.5/FTS/lib:/opt/sybase-12.5/OCS/lib:/
opt/sybase-12.5/SQLRemote/lib:/opt/sybase-12.5/lib
Any ideas?
Thanks
|
|
From: Andrew M. <an...@ob...> - 2004-03-12 06:07:56
|
>> I ask, because the error you reported doesn't say the library wasn't >> found, but rather that a symbol within the library wasn't found - which >> suggests to me that it found a library, but it was the wrong one. Is there > >Sure. I asked here about it because it seemed that setup.py setups up a >preprocessor macro that I suspected might have been intended to ifdef out >the offending use of blk_alloc on this particular setup. I should mention that I know next to nothing about the python-sybase module, although I've butted heads with Solaris for a few years now. I was hoping some general Solaris observations would help. 8-) -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |
|
From: John J L. <jj...@po...> - 2004-03-12 04:34:09
|
On Thu, 11 Mar 2004, Andrew McNamara wrote: [...] > I ask, because the error you reported doesn't say the library wasn't > found, but rather that a symbol within the library wasn't found - which > suggests to me that it found a library, but it was the wrong one. Is there Sure. I asked here about it because it seemed that setup.py setups up a preprocessor macro that I suspected might have been intended to ifdef out the offending use of blk_alloc on this particular setup. [...] > >> My immediate thought would be a different library is > >> being found at run-time compared to what setup.py sees (but this is just a > >> guess). > > > >We should just need SYBASE set properly in the environment, right? (and > >SYBASE_OCS, but I guess that's not the problem) I thought I'd done that > >right, but I can't swear to it. > > Uh - that would imply something somewhere was smart enough to use the > variable to set the run-time library search path on the resulting shared > library. Without something that fills the role of apache's apxs, this > probably won't happen. [...] That something was me ;-) I set LD_LIBRARY_PATH before importing the module. I just meant that SYBASE & SYBASE_OCS controls where setup.py finds things (and LD_LIBRARY_PATH controls where ld finds them). I'm pretty sure these were the values of the relevant environment variables: SYBASE /export/sybase/sybase_12.5 SYBASE_OCS OCS-12_5 LD_LIBRARY_PATH "/usr/local/lib:/export/sybase/sybase_12.5/OCS-12_5/lib" Unless I messed that up somehow, it should work, right? John |
|
From: Andrew M. <an...@ob...> - 2004-03-11 21:20:19
|
>> John - did the "symbol not found" error occur on the same machine as you >> built the module? > >Yes. I ask, because the error you reported doesn't say the library wasn't found, but rather that a symbol within the library wasn't found - which suggests to me that it found a library, but it was the wrong one. Is there any chance there's the ditritus from an old Sybase install on the machine? >> My immediate thought would be a different library is >> being found at run-time compared to what setup.py sees (but this is just a >> guess). > >We should just need SYBASE set properly in the environment, right? (and >SYBASE_OCS, but I guess that's not the problem) I thought I'd done that >right, but I can't swear to it. Uh - that would imply something somewhere was smart enough to use the variable to set the run-time library search path on the resulting shared library. Without something that fills the role of apache's apxs, this probably won't happen. As Jeff Younker suggests, try setting LD_LIBRARY_PATH to include the sybase lib directory and see if that helps. If it does, then you can try playing games with distutil to get the right -R option passed through to the linker, or just live with LD_LIBRARY_PATH (most people do the later... 8-) >> Andrew McNamara, Senior Developer, Object Craft > >Oh, hi again Andrew :-) I thought I recognized your name from >somewhere... Freaky. Small world. 8-) -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |
|
From: Jeff Y. <jyo...@of...> - 2004-03-11 19:27:49
|
The LD_LIBRARY_PATH needs to be set the the location of
the shared libs at runtime. Mine is set to:
${SYBASE_HOME}/OCS/lib
-jeff
|
|
From: Dave C. <dj...@ob...> - 2004-03-11 19:01:32
|
On Thu, 2004-03-11 at 10:39, John J Lee wrote: > On Wed, 10 Mar 2004, Andrew McNamara wrote: > [...] > > John - did the "symbol not found" error occur on the same machine as you > > built the module? > > Yes. > > > > My immediate thought would be a different library is > > being found at run-time compared to what setup.py sees (but this is just a > > guess). > > We should just need SYBASE set properly in the environment, right? (and > SYBASE_OCS, but I guess that's not the problem) I thought I'd done that > right, but I can't swear to it. I am not sure that distutils knows how to use the -R when building on Solaris. Hmm... There seems to be some code in there (distutils.unixcmpiler) to do it - I just am not sure it happens by default. - Dave -- http://www.object-craft.com.au |
|
From: John J L. <jj...@po...> - 2004-03-11 18:39:30
|
On Wed, 10 Mar 2004, Andrew McNamara wrote: [...] > John - did the "symbol not found" error occur on the same machine as you > built the module? Yes. > My immediate thought would be a different library is > being found at run-time compared to what setup.py sees (but this is just a > guess). We should just need SYBASE set properly in the environment, right? (and SYBASE_OCS, but I guess that's not the problem) I thought I'd done that right, but I can't swear to it. [...] > Andrew McNamara, Senior Developer, Object Craft Oh, hi again Andrew :-) I thought I recognized your name from somewhere... John |
|
From: Andrew M. <an...@ob...> - 2004-03-10 17:55:11
|
>Yes. At least, it does for everything I've tried. Gotta get the >LD_LIBRARY_PATH stuff right, esp. if you want the same .so to work for 11.5, >12.0 and 12.5 (which it seems to no problems). BTW, Solaris lets you specify a run-time library search path at link time with the -R linker option (it works like the -L option, which only has an effect at link-time under Solaris). John - did the "symbol not found" error occur on the same machine as you built the module? My immediate thought would be a different library is being found at run-time compared to what setup.py sees (but this is just a guess). -- Andrew McNamara, Senior Developer, Object Craft http://www.object-craft.com.au/ |
|
From: Gregory B. <gn...@it...> - 2004-03-10 17:27:37
|
jj...@po... said: > First, is the sybase module known to work with Sybase 12.5? Yes. At least, it does for everything I've tried. Gotta get the LD_LIBRARY_PATH stuff right, esp. if you want the same .so to work for 11.5, 12.0 and 12.5 (which it seems to no problems). |
|
From: John J L. <jj...@po...> - 2004-03-10 11:16:29
|
First, is the sybase module known to work with Sybase 12.5?
We compiled it (version 0.36) on Solaris (SunOS 5.8), but got a linker
error about blk_alloc:
>>> import Sybase
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "Sybase.py", line 20, in ?
from sybasect import *
ImportError: ld.so.1: /usr/local/bin/python: fatal: relocation error: file
./sybasect.so: symbol blk_alloc: referenced symbol not found
>>>
I notice (after having left the customer site, unfortunately) that use of
blk_alloc is conditional on HAVE_BLK_ALLOC, but since I'm new to Sybase I
have no idea what blk_alloc does, hence no idea whether it's safe to leave
it out of a build by hacking setup.py. Any clues?
Presumably setup.py found CS_PUBLIC_BLK_ALLOC in bkpulic.h, or
HAVE_BLK_ALLOC would have been undefined, so I'm not sure why the symbol
isn't found.
> ldd sybasect.so
libsybdb.so => /export/sybase/sybase_12.5/OCS-12_5/lib/libsybdb.so
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libc.so.1 => /usr/lib/libc.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libmp.so.2 => /usr/lib/libmp.so.2
/usr/platform/SUNW,Ultra-Enterprise-10000/lib/libc_psr.so.1
nm confirms that there's no blk_alloc in
/export/sybase/sybase_12.5/OCS-12_5/lib/libsybdb.so
Thanks in advance for any help
John
|
|
From: Dave C. <dj...@ob...> - 2004-02-26 19:35:46
|
Sorry for my unresponsiveness of late, I am completely snowed under with work (and have been for some time now). I do not have the time to do development work on the Sybase module, but I will make time to integrate patches. If people are willing to send patches I will integrate them and issue releases. - Dave -- http://www.object-craft.com.au |
|
From: Karl D. <die...@my...> - 2004-02-25 12:42:04
|
This problem has been brought up before. see: https://www.object-craft.com.au/pipermail/python-sybase/2003-December/000202.html When an SQL command with an error is sent (for example a query from a table that doesn't exist). When you try to use the connection again (with the corrected SQL for example) you get an error like: Traceback (most recent call last): File "/usr/local/lib/python2.3/site-packages/Sybase.py", line 157, in _clientmsg_cb raise DatabaseError(_fmt_client(msg)) Sybase.DatabaseError: Layer: 1, Origin: 1 ct_cmd_drop(): user api layer: external error: This routine can be called only if the command structure is idle. I think it would be better to send a warning and return the connection to a usable state. My particular problem is that Sybase connects to my default database first and then switches to the database I specified. I have to log into several Sybase server instances and when I log into a server that doesn't have my default database I get an error every time so I can never get connected. -- Karl Diedrich Programmer III Myriad Genetics, Inc. 320 Wakara Way Salt Lake City, UT 84108 http://www.myriad.com/ (801) 883-3246 |
|
From: Pavel <ach...@pi...> - 2004-02-13 03:50:46
|
Hello
Please look at the following:
>>> import Sybase
>>> db = Sybase.connect('sybase_server', '*', '*', 'xcvb')
>>> c = db.cursor()
>>> c.execute('ERROR_STATEMENT')
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 687, in execute
self.description = fetcher.start(self.arraysize)
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 442, in start
return self._start_results()
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 546, in _start_results
status, result = self._cmd.ct_results()
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 161, in _servermsg_cb
raise DatabaseError(_fmt_server(msg))
Sybase.DatabaseError: Msg 2812, Level 16, State 5, Line 1
Stored procedure 'ERROR_STATEMENT' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).
>>> c.close()
>>> db.rollback()
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 889, in rollback
self.execute('rollback transaction')
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 906, in execute
fetcher.start(self.arraysize)
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 260, in start
status = self._cmd.ct_send()
File "/usr/local/python/lib/python2.3/site-packages/Sybase.py", line 157, in _clientmsg_cb
raise DatabaseError(_fmt_client(msg))
Sybase.DatabaseError: Layer: 1, Origin: 1
ct_send(): user api layer: external error: This routine cannot be called because another command structure has results pending.
>>>
what am I doing wrong?
|
|
From: <m.a...@ri...> - 2004-01-14 05:39:50
|
Hi I am trying to build: sybase-0.36 I am using Adaptive Sever Anywhere Database 6.0.01. When I try to run the 'python setup.py install' it stops complaining that=20 it cannot find the sybase\include directory - hence 'cannot build'. I cannot find this ominous 'include' directory - Neither on my "client"=20 nor on the "sybase server". Where can I get this 'includes'? Is it only=20 available for > ASA 6.XXX? What else can I do? Thanks for any suggestions, Greetings, Marco Marco Aschwanden Fisch Asset Management Postfach 977 Gartenstrassse 19 8039 Z=FCrich Tel.: +41 1 284 24 42 E-Mail: m.a...@ri... Vizitu nian retpagxon: http://www.riskreturn.ch |
|
From: David C. <da...@ne...> - 2004-01-04 00:19:04
|
Hello, I'm trying to build 0.36 on MacOS X 10.3 with Sybase ASE 12.5.1 installed. The installer is choking on sybasect -- building 'sybasect' extension gcc -Wl,-F. -Wl,-F. -bundle -framework Python build/temp.darwin-7.2.0-Power_Macintosh-2.3/blk.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/databuf.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/cmd.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/conn.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/ctx.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/datafmt.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/iodesc.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/locale.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/msgs.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/numeric.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/money.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/datetime.o build/temp.darwin-7.2.0-Power_Macintosh-2.3/sybasect.o -L/Applications/Sybase/System/OCS-12_5/lib -o build/lib.darwin-7.2.0-Power_Macintosh-2.3/sybasect.so ld: Undefined symbols: _blk_alloc _blk_bind _blk_describe (and about 50 other symbols) -- but all of these symbols are present in libraries which can be found at /Applications/Sybase/System/OCS-12_5/lib, clearly pointed to by gcc's -L flag. Any suggestions? David. |
|
From: <msa...@gr...> - 2004-01-03 04:52:09
|
In my company (medium sized, public administration oriented), we use it
to access MS SQL Server from Linux. But we don't use parameters when
using this modules.
Peter Hansack wrote:
> Sybase ASE uses parameters positional (in the order they are defined in
> ct_param) - even named parameters.
>
> An example:
>
> ----------------------
> import Sybase
>
> db = Sybase.connect('SYBASE','sa','',database='data',auto_commit=1)
>
> db.execute('''create table test (
> key1 varchar(10) not null,
> value1 varchar(10) null,
> value2 varchar(10) null,
> value3 varchar(10) null,
> value4 varchar(10) null,
> value5 varchar(10) null )
> ''')
>
> # 1 #
> v = { '@key1' : 'key1', '@value1' : 'value1', '@value2' : 'value2',
> '@value3' : 'value3', '@value4' : 'value4', '@value5' : 'value5'}
> print "v=", v
>
> c = db.cursor()
>
> # 2 #
> c.execute('insert into test values
> (@key1,@value1,@value2,@value3,@value4,@value5)',v)
>
> # 3 #
> c.execute('select * from test')
> x = c.fetchone()
> print "x=", x
>
> # 4 #
> c.execute('''select * from test where key1=@key1 and value1=@value1
> and value2=@value2 and value3=@value3 and value4=@value4
> and value5=@value5''',v)
>
> y = c.fetchone()
> print "y=", y
>
> c.close()
> db.close()
> ----------------------
>
>
> Running the example gives the following output:
>
> v= {'@key1': 'key1', '@value4': 'value4', '@value5': 'value5', '@value2':
> 'value2', '@value3': 'value3', '@value1': 'value1'}
> x= ('key1', 'value4', 'value5', 'value2', 'value3', 'value1')
> y= ('key1', 'value4', 'value5', 'value2', 'value3', 'value1')
>
>
> Conclusion:
> # 3 # shows, that in insert the parameters are applied not in the order of #
> 2 #, but in the order
> shown in # 1 # (i.e in the incidental internal order of the dictionary) and
> # 4 # shows, that this is
> true also for where-clauses.
>
>
> Consequence: a patch (for 0.36)
>
> # diff Sybase.py.original Sybase.py
> 246a247,249
>
>>import re
>>re_params = re.compile(r'@\w+')
>>
>
> 681c684,685
> < for name, value in params.items():
> ---
>
>> for name in re_params.findall(sql):
>> value = params[name]
>
>
> This helps only in cursor.execute(); the rest of the module should be
> checked also.
>
>
> Question: Is anybody using this module?
>
>
> Regards,
>
|
3 messages has been excluded from this view by a project administrator.
