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: Dan H. <dan...@re...> - 2019-05-03 00:36:07
|
Thanks. I finally got it working after installing python-sybase-0.40pre2.tar.gz <http://downloads.sourceforge.net/python-sybase/python-sybase-0.40pre2/python-sybase-0.40pre2.tar.gz>. I had assumed that the "pre" versions weren't production-ready, but I gave it a go anyway. I'll have a look at the ODBC alternatives On Fri, 3 May 2019 at 11:27, Bond, Gregory <GB...@vi...> wrote: > This module is mostly abandoned now that Sybase supports ODBC drivers. > You’d be better to look at pyodbc/unixodbc packages, assuming it’s > supported on your platform. > > > > *From:* Dan Horne <dan...@re...> > *Sent:* Friday, 3 May 2019 7:36 AM > *To:* pyt...@li... > *Subject:* [Python-sybase-misc] Unable to import Sybase library > > > > Hi > > > > As a test of the Python-sybase install I get: > > > > # python > > Python 2.7.5 (default, Sep 12 2018, 05:31:16) > > [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2 > > Type "help", "copyright", "credits" or "license" for more information. > > >>> import Sybase > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > File "build/bdist.linux-x86_64/egg/Sybase.py", line 11, in <module> > > File "build/bdist.linux-x86_64/egg/sybasect.py", line 7, in <module> > > File "build/bdist.linux-x86_64/egg/sybasect.py", line 6, in __bootstrap__ > > ImportError: > /root/.python-eggs/python_sybase-0.39-py2.7-linux-x86_64.egg-tmp/sybasect.so: > undefined symbol: ct_callback > > > > So I ran ldd > > > > # ldd > /root/.python-eggs/python_sybase-0.39-py2.7-linux-x86_64.egg-tmp/sybasect.so > > linux-vdso.so.1 => (0x00007ffc5614c000) > > libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 > (0x00007f91552e3000) > > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f91550c7000) > > libc.so.6 => /lib64/libc.so.6 (0x00007f9154cfa000) > > libdl.so.2 => /lib64/libdl.so.2 (0x00007f9154af6000) > > libutil.so.1 => /lib64/libutil.so.1 (0x00007f91548f3000) > > libm.so.6 => /lib64/libm.so.6 (0x00007f91545f1000) > > /lib64/ld-linux-x86-64.so.2 (0x00007f91558d2000) > > > > We are using FreeTDS (0.95.81). I'm pretty sure that it's installed > correctly since I can connect from Perl via DBD::Sybase (note I'm a Perl > programmer, not a Python one, but I need to set this up for Python devs. > Hence I may be missing/misunderstanding things) > > > > > > > > This message, including any attachments, is intended only for the personal > and confidential use of the designated recipient(s) to which it is > addressed. This communication may contain information that constitutes > attorney work product, is privileged, confidential or otherwise protected > from disclosure. If the reader of this message is not the designated > recipient, you are hereby notified that you have received this > communication in error, and that any review, dissemination, retention, > distribution or copying of this communication is strictly prohibited. If > you have received this communication in error, please notify us by e-mail > reply to the sender, and discard any paper copies and delete all electronic > files of this communication. This communication is for informational > purposes only and has been obtained from sources believed to be reliable, > but it is not necessarily complete and its accuracy cannot be guaranteed. > It is not intended as an offer or solicitation for the purchase or sale of > any financial instrument or as an official confirmation of any transaction. > Moreover, this material should not be construed to contain any > recommendation regarding, or opinion concerning, any security. Any views > expressed in this message are those of the individual sender, except where > the message states otherwise and the sender is authorized to state them to > be the views of any such entity. > > Virtu ITG Hong Kong Limited is licensed by the Securities and Futures > Commission of Hong Kong, Virtu ITG Singapore Pte Limited is licensed by the > Monetary Authority of Singapore and Virtu ITG Australia Limited is licensed > by the Australian Securities and Futures Commission. > > Virtu and/or its affiliates reserve the right to monitor and archive all > electronic communications through its network. Virtu Financial LLC > <http://www.virtu.com/>. > > > > |
From: Dan H. <dan...@re...> - 2019-05-02 22:06:41
|
Hi As a test of the Python-sybase install I get: # python Python 2.7.5 (default, Sep 12 2018, 05:31:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import Sybase Traceback (most recent call last): File "<stdin>", line 1, in <module> File "build/bdist.linux-x86_64/egg/Sybase.py", line 11, in <module> File "build/bdist.linux-x86_64/egg/sybasect.py", line 7, in <module> File "build/bdist.linux-x86_64/egg/sybasect.py", line 6, in __bootstrap__ ImportError: /root/.python-eggs/python_sybase-0.39-py2.7-linux-x86_64.egg-tmp/sybasect.so: undefined symbol: ct_callback So I ran ldd # ldd /root/.python-eggs/python_sybase-0.39-py2.7-linux-x86_64.egg-tmp/sybasect.so linux-vdso.so.1 => (0x00007ffc5614c000) libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f91552e3000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f91550c7000) libc.so.6 => /lib64/libc.so.6 (0x00007f9154cfa000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f9154af6000) libutil.so.1 => /lib64/libutil.so.1 (0x00007f91548f3000) libm.so.6 => /lib64/libm.so.6 (0x00007f91545f1000) /lib64/ld-linux-x86-64.so.2 (0x00007f91558d2000) We are using FreeTDS (0.95.81). I'm pretty sure that it's installed correctly since I can connect from Perl via DBD::Sybase (note I'm a Perl programmer, not a Python one, but I need to set this up for Python devs. Hence I may be missing/misunderstanding things) |
From: Skip M. <sk...@po...> - 2016-10-06 13:01:18
|
On Wed, Oct 5, 2016 at 4:56 PM, Skip Montanaro <sk...@po...> wrote: > > Valgrind complains about ctx_alloc I think. I don't have that output in front of me at the moment. I'll pass along an error message tomorrow. Here's one example. All seem to be similar, reading off the end of a malloc'd chunk of memory. I just ran valgrind over the Py2 version and got no such read errors, so I suspect my problems are caused by issues related to structure sizes. Just to make sure it wasn't related to configuring my Python build using --with-pydebug, I rebuilt from scratch without it, and get the same errors. I might well have messed something up in the conversion of the module init code. I'll take a look at whatever explicit allocation the code does. Skip ==28701== Invalid read of size 4 ==28701== at 0xCF223A9: com__err_load_errors (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcomn_r64.so) ==28701== by 0xCF231A4: com_err_init (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcomn_r64.so) ==28701== by 0xCCE37F4: cs__errinit (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcs_r64.so) ==28701== by 0xCCDFFEC: cs_ctx_alloc (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcs_r64.so) ==28701== by 0xC3DBD42: ctx_alloc (ctx.c:1425) ==28701== by 0xC3E3A59: sybasect_cs_ctx_alloc (sybasect.c:177) ==28701== by 0x4D7ECF: PyCFunction_Call (methodobject.c:109) ==28701== by 0x5DB7CB: call_function (ceval.c:4723) ==28701== by 0x5D3982: PyEval_EvalFrameEx (ceval.c:3277) ==28701== by 0x5D86FD: _PyEval_EvalCodeWithName (ceval.c:4036) ==28701== by 0x5D8864: PyEval_EvalCodeEx (ceval.c:4057) ==28701== by 0x5BF14B: PyEval_EvalCode (ceval.c:777) ==28701== Address 0x70afcc4 is 4 bytes inside a block of size 6 alloc'd ==28701== at 0x4C2ABED: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==28701== by 0xCF221DD: com__err_load_errors (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcomn_r64.so) ==28701== by 0xCF231A4: com_err_init (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcomn_r64.so) ==28701== by 0xCCE37F4: cs__errinit (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcs_r64.so) ==28701== by 0xCCDFFEC: cs_ctx_alloc (in /opt/local/encap/sybase15_7-15.7.110+1/sybase-15.7/OCS-15_0/lib/libsybcs_r64.so) ==28701== by 0xC3DBD42: ctx_alloc (ctx.c:1425) ==28701== by 0xC3E3A59: sybasect_cs_ctx_alloc (sybasect.c:177) ==28701== by 0x4D7ECF: PyCFunction_Call (methodobject.c:109) ==28701== by 0x5DB7CB: call_function (ceval.c:4723) ==28701== by 0x5D3982: PyEval_EvalFrameEx (ceval.c:3277) ==28701== by 0x5D86FD: _PyEval_EvalCodeWithName (ceval.c:4036) ==28701== by 0x5D8864: PyEval_EvalCodeEx (ceval.c:4057) |
From: Skip M. <sk...@po...> - 2016-10-05 21:56:55
|
Thanks for the reply, Sébastien. As I only have another couple days left at my current job, I am unlikely to do much more with it. It still builds and seems to run okay on Python 2. I get an early core dump from the Python 3 code. Valgrind complains about ctx_alloc I think. I don't have that output in front of me at the moment. I'll pass along an error message tomorrow. I did a checkout from the Subversion repo, so hopefully I am using the latest code. I do notice that it still says "0.40" though. Skip On Tue, Apr 20, 2010 at 9:12 AM, Sébastien Sablé < sa...@us...> wrote: > Hi Mic, > > great to hear about that SQLAlchemy will support Sybase. > > You should note that python-sybase is unfortunately not perfectly DBAPI > compliant because of some limitations of sybase which make it hard to > perfectly follow the specification (problems with nested requests > notably). If you encounter such problem, and can reproduce it with a > unitary test, I would be happy to help correct it in python-sybase. > > Also please note that the trunk has quite a lot of bug corrections > compared to the last release, so I would suggest to use it rather than > the latest official release (I should take some time to make a new > release). > > The development of python-sybase is rather slow at the moment; I work on > it for the needs of a legacy project at my work, but Sybase is not the > priority at the moment and so I mostly do maintenance and small bug > corrections. I didn't have time to make a proper release for a long > time, though I hope to have more free time for that this summer. > > At some stage we will have to get the legacy project on which I work to > support sybase in the latest version. When that will happen I will be > able to dedicate a full month or 2 to improve python-sybase, mostly > concerning performances (and unicode support). I should be able to also > check Python 3 compatibility at the same time. But in the meantime, I > can only ensure small bugs corrections and answering to emails. > > regards > > -- > Sébastien Sablé > > > > Michael Bayer a écrit : > > Hi there - > > > > I just wanted to give the developers a heads up that SQLAlchemy 0.6 will > > feature a new Sybase ASE dialect that defaults to using Python-Sybase as > > its backend. I finally got a test ASE server up over the weekend and > > managed to get a rudimental Sybase conversation going on with this > driver. > > > > Was also wondering about the development schedule of the driver, I see > the > > last release was in 2008. Are there any plans to add Python 3 support to > > this driver ? When installing via Distribute, if the setup.py file > > specifies a "2to3" flag then Distribute will automatically run the source > > code through the 2to3 tool before installing. I've now created Python 3 > > versions of three different libraries (Mako, Beaker, SQLAlchemy) in this > > way and its pretty straightforward. > > > > thanks for your efforts on this driver ! > > > > - mike > > > > ------------------------------------------------------------ > ------------------ > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Python-sybase-misc mailing list > > Pyt...@li... > > https://lists.sourceforge.net/lists/listinfo/python-sybase-misc > > > > > ------------------------------------------------------------ > ------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Python-sybase-misc mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-sybase-misc > |
From: Skip M. <sk...@po...> - 2014-03-14 14:46:48
|
Looking here: http://sourceforge.net/projects/python-sybase/files/python-sybase/ I see a python-sybase-0.40 folder that's newer than python-sybase-0.40pre2. When I decend into that folder though, I get this message: Looking for the latest version? Download python-sybase-0.40pre2.tar.gz (127.1 kB) Apparently, 0.40 was never officially released? Can someone comment? I see a checkin message by Rob about reverting some NULL data handling. That seems to be the only difference. Skip |
From: Skip M. <sk...@po...> - 2014-03-13 15:00:10
|
> Given this simple stored procedure: > > create stored procedure test_proc > as > return 1 > > Is there a way in 0.40pre2 to get the return value? I believe I have this figured out. There is a bug in the handling of the status result. Unlike 0.38 and earlier, the return value of the stored procedure is processed. Unfortunately, it's saved to a local variable instead of in an attribute of the Cursor object. I've attached a proposed patch. The user here who was stung by this thinks it's the proper fix. Hopefully someone is reading this (Rob?, Sebastien? Andrew? Dave?) and can comment on its accuracy. Skip |
From: Skip M. <sk...@po...> - 2014-03-13 11:15:20
|
> Given this simple suited procedure: Stupid predictive typing system... s/suited/stored/g S |
From: Skip M. <sk...@po...> - 2014-03-13 02:33:03
|
Given this simple suited procedure: create stored procedure test_proc as return 1 Is there a way in 0.40pre2 to get the return value? Thx, Skip |
From: Skip M. <sk...@po...> - 2013-11-04 20:32:16
|
I understand that to allocate space for output parameters of stored procedures you call the Sybase.OUTPUT() function with an appropriate type. I can't figure out what to do with the resulting output parameter dictionary's value. If my input parameters contain such and OUTPUT() function result: params = { ... '@result': Sybase.OUTPUT(1), ... } the return value is a dictionary whose "@result" key is an instance of DataBufType. None of the attributes of that instance seem to suggest how to extract the actual output value in terms of a usable Python data type. How do I get that value? Thx, Skip Montanaro |
From: Skip M. <sk...@po...> - 2013-10-31 23:18:57
|
> Traceback (most recent call last): > File "<pyshell#0>", line 1, in <module> > import Sybase > File "build\bdist.win32\egg\Sybase.py", line 15, in <module> > File "build\bdist.win32\egg\sybasect.py", line 7, in <module> > File "build\bdist.win32\egg\sybasect.py", line 6, in __bootstrap__ > ImportError: DLL load failed: The specified module could not be found. Underlying the sybasect module is probably an _sybasect.dll file. (I'm not a Windows user, and am unfamiliar with the exact details of how the various modules and DLLs are layered atop one another to provide you with a functioning Sybase import.) Either _sybasect.dll is missing or some other DLL it relies on is missing. Take a look at the sybasect.py file and see what it imports around or in the __bootstrap__ function. Skip |
From: <Tao...@rb...> - 2013-10-31 20:37:33
|
Hi, I've been using python-sybase-0.40pre1 without a hitch for couple of years. All of a sudden I started having the following problem on one of my boxes. Python 2.7.5 (default, May 15 2013, 22:43:36) [MSC v.1500 32 bit (Intel)] on win32 Type "copyright", "credits" or "license()" for more information. >>> import Sybase Traceback (most recent call last): File "<pyshell#0>", line 1, in <module> import Sybase File "build\bdist.win32\egg\Sybase.py", line 15, in <module> File "build\bdist.win32\egg\sybasect.py", line 7, in <module> File "build\bdist.win32\egg\sybasect.py", line 6, in __bootstrap__ ImportError: DLL load failed: The specified module could not be found. >>> I am using windows xp sp3. Sybase module works fine on another box that is identical in terms of hardware and os setup. Both boxes have the same set of dlls in c:\Windows\system32. Reinstall/reboot or 0.40pre2 didn't fix the problem. What could be the problem? Thanks, Tao ******************************************************************** Invitation to consider a derivatives transaction: This communication, where prepared by the sales and trading desk or desk strategists, may be marketing material, desk strategy and/or trader commentary. It is not a product of the research department. This material may constitute an invitation to consider entering into a derivatives transaction under U.S. CFTC Regulations §§ 1.71 and 23.605, where applicable, but is not a binding offer to buy/sell any financial instrument. The views of the author may differ from others at The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V. and/or RBS Securities Inc. (collectively "RBS"). This message (including any attachments) is confidential and/or privileged. It is to be used by the intended recipients only. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are inherently insecure and susceptible to change. The Royal Bank of Scotland Group, plc ("RBS") and its subsidiaries, and affiliates and subsidiary undertakings, including but not limited to, RBS plc New York and Connecticut Branches, RBS Securities Inc., The Royal Bank of Scotland N.V. New York and Chicago Branches (formerly named ABN AMRO Bank N.V.), Citizens Financial Group, Inc. and RBS Citizens, N.A., shall not be liable for the improper or incomplete transmission of the information contained in this communication or Attachment nor for any delay in its receipt or damage to your system. RBS does not guarantee that the integrity of this communication has been maintained nor that this communication is free of viruses, interceptions or interference. For the protection of RBS and its clients and customers, and in compliance with regulatory requirements, the contents of both incoming and outgoing e-mail communications, which could include proprietary information and non-public personal information (‘NPPI’), may be reviewed. RBS and its subsidiaries and affiliates do not guarantee the accuracy of any email or attachment, that an email will be received or that RBS or its affiliates and subsidiaries will respond to an email. RBS makes no representations that any information contained in this message (including any attachments) are appropriate for use in all locations or that transactions, securities, products, instruments or services discussed herein are available or appropriate for sale or use in all jurisdictions, or by all investors or counterparties. Those who utilize this information do so on their own initiative and are responsible for compliance with applicable local laws or regulations. USA PATRIOT Act Customer Notice: To help the government fight the funding of terrorism and money laundering activities, federal law requires all U.S. financial institutions to obtain, verify, and record information that identifies each customer who opens an account. What this means to our customers: When we open an account on your behalf or we provide services to a business entity, we will ask for its name and address as well as a tax identification number for U.S. entities or other government issued identification number for non-US entities. In addition, we may also ask for documents and/or information relating to the business's formation as well as its principals and/or beneficial owners. ******************************************************************** |
From: malisetti r. <mal...@gm...> - 2013-10-05 10:55:41
|
Hi Paul, Thanks for spending time to reply me for the post. Even i tried with python-sybase, it is getting me compilation errors with the downloaded tar ball. I have tried compilation on Ubuntu 10.04 OS. If you could provide me debian package for python-sybase module, that would be helpful for me. Thank You, Ram Murthy On Tue, Oct 1, 2013 at 9:49 PM, Ram Murthy <mal...@gm...>wrote: > Hello Readers, > > I have a bit tricky problem with establishing the sybase db connection > with python-pymssql module. I am not sure what the error messages exactly > mean. The sybase db is residing on the remote host and i am trying to > access it with a python script. > > I am getting the following errors messages : > > I) > >>> con=pymssql.connect(user='<**host-username>', > password='<host-password>', host='<host-ip>:', database='<db-name>') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/pymodules/python2.6/**pymssql.py", line 607, in connect > raise OperationalError, e[0] > pymssql.OperationalError: DB-Lib error message 20009, severity 9: > Unable to connect: Adaptive Server is unavailable or does not exist > Net-Lib error during Operation now in progress Error 115 - Operation now > in progress > -------------------------- > > II) > >>> con=pymssql.connect(user='<**host-username>', > password='<host-password>', host='<host-ip>:5150', database='<db-name>') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/pymodules/python2.6/**pymssql.py", line 609, in connect > raise InterfaceError, e[0] pymssql.InterfaceError: Could not set > connection properties > > > Any suggestions or answers would be helpful. > > And one thing, is there any another way for connecting to the Sybase DB > hosted on the remote AIX machine through python / perl script. > > > Thank You, > Ram Murthy > > |
From: Paul E. <pa...@ec...> - 2013-10-04 19:24:39
|
On Oct 1, 2013, at 18:19, Ram Murthy <mal...@gm...> wrote: > Hello Readers, > > I have a bit tricky problem with establishing the sybase db connection > with python-pymssql module. I am not sure what the error messages > exactly mean. The sybase db is residing on the remote host and i am > trying to access it with a python script. > > I am getting the following errors messages : > > I) >>>> con=pymssql.connect(user='<host-username>', > password='<host-password>', host='<host-ip>:', database='<db-name>') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/pymodules/python2.6/pymssql.py", line 607, in connect > raise OperationalError, e[0] > pymssql.OperationalError: DB-Lib error message 20009, severity 9: > Unable to connect: Adaptive Server is unavailable or does not exist > Net-Lib error during Operation now in progress Error 115 - Operation now > in progress > -------------------------- > > II) >>>> con=pymssql.connect(user='<host-username>', > password='<host-password>', host='<host-ip>:5150', database='<db-name>') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/usr/lib/pymodules/python2.6/pymssql.py", line 609, in connect > raise InterfaceError, e[0] pymssql.InterfaceError: Could not set > connection properties > > > Any suggestions or answers would be helpful. > > And one thing, is there any another way for connecting to the Sybase DB > hosted on the remote AIX machine through python / perl script. > > > Thank You, > Ram Murthy > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Python-sybase-misc mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-sybase-misc Hi Ram! I'm not sure you posted to the right list.. You are using pymssql (http://code.google.com/p/pymssql/), this list is about the python-sybase (http://sourceforge.net/projects/python-sybase/) module. All the best Paul |
From: Ram M. <mal...@gm...> - 2013-10-01 16:19:39
|
Hello Readers, I have a bit tricky problem with establishing the sybase db connection with python-pymssql module. I am not sure what the error messages exactly mean. The sybase db is residing on the remote host and i am trying to access it with a python script. I am getting the following errors messages : I) >>> con=pymssql.connect(user='<host-username>', password='<host-password>', host='<host-ip>:', database='<db-name>') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/pymodules/python2.6/pymssql.py", line 607, in connect raise OperationalError, e[0] pymssql.OperationalError: DB-Lib error message 20009, severity 9: Unable to connect: Adaptive Server is unavailable or does not exist Net-Lib error during Operation now in progress Error 115 - Operation now in progress -------------------------- II) >>> con=pymssql.connect(user='<host-username>', password='<host-password>', host='<host-ip>:5150', database='<db-name>') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/pymodules/python2.6/pymssql.py", line 609, in connect raise InterfaceError, e[0] pymssql.InterfaceError: Could not set connection properties Any suggestions or answers would be helpful. And one thing, is there any another way for connecting to the Sybase DB hosted on the remote AIX machine through python / perl script. Thank You, Ram Murthy |
From: Skip M. <sk...@po...> - 2013-06-21 01:14:45
|
On Thu, Jun 20, 2013 at 4:59 PM, Kevin Stone <Kev...@ja...> wrote: > The problem is not that queries take a long time. The problem is that queries are not being executed in parallel. All it takes is for one user to run a query (it does not have to be a long one, maybe a few seconds), and the entire app will be down until that query finishes. > > I am using python 2.7 on linux with freeTDS against sybase 15. Rob and I discussed this a little bit off-line (we happen to work at the same Sybase-using company). A quick glance last night suggested to me that the python-sybase code does its own GIL releasing and acquiring, not relying on the macros Python provides for this purpose. It's possible that over time the GIL-handling code in Python has changed, and the code in python-sybase hasn't kept up. Just to be confirm though, your other threads are threads are not even into the Sybase part of the system, correct? They aren't blocking because the first query has locked resources in the server? I'll try to take a look more closely at GIL-handling code tomorrow. Skip |
From: Kevin S. <Kev...@ja...> - 2013-06-20 21:59:36
|
The problem is not that queries take a long time. The problem is that queries are not being executed in parallel. All it takes is for one user to run a query (it does not have to be a long one, maybe a few seconds), and the entire app will be down until that query finishes. I am using python 2.7 on linux with freeTDS against sybase 15. -Kevin ________________________________________ From: Robert Boehne [ro...@tr...] Sent: Thursday, June 20, 2013 5:25 PM To: pyt...@li... Subject: Re: [Python-sybase-misc] handling multiple threads On 06/19/13 15:26, Kevin Stone wrote: > I am trying to develop a python webapp using pysybase that is pretty > basic. I want to be able to create SQL QC reports that our users can > update on demand as they edit the database. > > However, I am having problems getting this to work in a multi-threaded > environment like cherrypy. If I execute one long query, no new > connections can be made, in fact all other threads come to a halt > until that one query returns. Is this something that is not supported > by this driver? > > Here is a sample test that I've been using: > > def sy_query(query): > db = Sybase.connect(dbServer,dbUser,dbPass,dbName) > cur = db.cursor() > cur.execute(query) > t1 = Thread(target=sy_query,args=("select * from blah",)) > t2 = Thread(target=sy_query,args=("select something from blah2",)) > t1.start() > t2.start() > t1.join() > t2.join() > > > As soon as thread 1 calls "status = ct_results(self->cmd, &result);" > inside of cmd.c nothing happens in either the main function nor in > thread 2. > Immediately after that line finishes, everything moves along. > > Any suggestions? I can't have a webapp that only works for one user at > a time. > > -Kevin It is the intent that everything done in C calls to Sybase would release the GIL and can run in different threads concurrently. However, this code hasn't had a lot of maintenance recently, and so may suffer from being out of sync with modern python versions. So if you're queries take a long time (like a minute) then we'd need to determine what your specific configuration is. What version of Sybase are you linked to, what platform are you on, and what version of python are you running? Thanks, Robert Boehne ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Python-sybase-misc mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/python-sybase-misc The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible. |
From: Robert B. <ro...@tr...> - 2013-06-20 21:48:05
|
On 06/19/13 15:26, Kevin Stone wrote: > I am trying to develop a python webapp using pysybase that is pretty > basic. I want to be able to create SQL QC reports that our users can > update on demand as they edit the database. > > However, I am having problems getting this to work in a multi-threaded > environment like cherrypy. If I execute one long query, no new > connections can be made, in fact all other threads come to a halt > until that one query returns. Is this something that is not supported > by this driver? > > Here is a sample test that I've been using: > > def sy_query(query): > db = Sybase.connect(dbServer,dbUser,dbPass,dbName) > cur = db.cursor() > cur.execute(query) > t1 = Thread(target=sy_query,args=("select * from blah",)) > t2 = Thread(target=sy_query,args=("select something from blah2",)) > t1.start() > t2.start() > t1.join() > t2.join() > > > As soon as thread 1 calls "status = ct_results(self->cmd, &result);" > inside of cmd.c nothing happens in either the main function nor in > thread 2. > Immediately after that line finishes, everything moves along. > > Any suggestions? I can't have a webapp that only works for one user at > a time. > > -Kevin It is the intent that everything done in C calls to Sybase would release the GIL and can run in different threads concurrently. However, this code hasn't had a lot of maintenance recently, and so may suffer from being out of sync with modern python versions. So if you're queries take a long time (like a minute) then we'd need to determine what your specific configuration is. What version of Sybase are you linked to, what platform are you on, and what version of python are you running? Thanks, Robert Boehne |
From: Kevin S. <Kev...@ja...> - 2013-06-19 20:26:14
|
I am trying to develop a python webapp using pysybase that is pretty basic. I want to be able to create SQL QC reports that our users can update on demand as they edit the database. However, I am having problems getting this to work in a multi-threaded environment like cherrypy. If I execute one long query, no new connections can be made, in fact all other threads come to a halt until that one query returns. Is this something that is not supported by this driver? Here is a sample test that I've been using: def sy_query(query): db = Sybase.connect(dbServer,dbUser,dbPass,dbName) cur = db.cursor() cur.execute(query) t1 = Thread(target=sy_query,args=("select * from blah",)) t2 = Thread(target=sy_query,args=("select something from blah2",)) t1.start() t2.start() t1.join() t2.join() As soon as thread 1 calls "status = ct_results(self->cmd, &result);" inside of cmd.c nothing happens in either the main function nor in thread 2. Immediately after that line finishes, everything moves along. Any suggestions? I can't have a webapp that only works for one user at a time. -Kevin The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible. |
From: Robert B. <ro...@tr...> - 2012-06-11 20:46:08
|
WHAT IS IT: The Sybase module provides a Python interface to the Sybase relational database system. It supports all of the Python Database API, version 2.0 with extensions. The module is available here: http://downloads.sourceforge.net/python-sybase/python-sybase-0.40.tar.gz The module home page is here: http://python-sybase.sourceforge.net/ MAJOR CHANGES SINCE 0.39: Modify the DateTimeAsPython output conversion to return None when NULL is output support for Python without threads Ignore additional non-error codes from Sybase (1918 and 11932) Use outputmap in bulkcopy mode (thanks to patch by Cyrille Froehlich) Raise exception when opening a cursor on a closed connection Added unit tests Added new exception DeadLockError when Sybase is in a deadlock situation Add command properties CS_STICKY_BINDS and CS_HAVE_BINDS Added support for inputmap in bulkcopy reuse command and cursor when calling cursor.execute with same request Use ct_setparam to define ct_cursor parameters types instead of ct_param implicit conversion for CS_DATE_TYPE in CS_DATETIME_TYPE DataBuf Adding ct_cmd_props wrapper Increase DataBuf maxlength for params of a request when using CS_CHAR_TYPE params so that the buf can be reused BUGS CORRECTED SINCE 0.39: Corrected money type when using CS_MONEY4 (close bug 2615821) Corrected thread locking in ct_cmd_props (thanks to patch by Cyrille Froehlich) Corrected bug in type mapping in callproc (thanks to report by Skip Montanaro) Correct passing None in a DataBuf (thanks to patch by Bram Kuijvenhoven) The full ChangeLog is here: https://python-sybase.svn.sourceforge.net/svnroot/python-sybase/tags/r0_40/ChangeLog |
From: Henrik P. <hen...@gm...> - 2012-01-17 18:45:20
|
Hello. I am trying to retrieve a money value (in 0.39) from a table and noticed that the value '5.3333' would get fetched out as '5.33' when I print it. It has me stumped. Is there some way to get the value so I retain the scale or is this a limitation/bug in python-sybase or am I just missing something? Best regards, Henrik Poulsen |
From: slav0nic <sla...@gm...> - 2012-01-10 08:16:15
|
Hi, i used 0.39 version. Exist any way for set connection timeout for Sybase.connect()? When i connected to nonexistent IP script freeze (but isql return error after ~60sec) + connect locked all threads ( not thread-safe?):| socket.setdefaulttimeout() does't work for C extensions Tnx |
From: Robert B. <ro...@tr...> - 2011-12-08 20:08:34
|
WHAT IS IT: The Sybase module provides a Python interface to the Sybase relational database system. It supports all of the Python Database API, version 2.0 with extensions. Please downolad, test and report any problems with the pre-release. ** This version is a pre-release not intended for production use ** The module is available here: http://downloads.sourceforge.net/python-sybase/python-sybase-0.40pre2.tar.gz The module home page is here: http://python-sybase.sourceforge.net/ MAJOR CHANGES SINCE 0.40pre1: Better support for building against Sybase 15 on Windows, UNIX/Linux and 64-bit platforms. MAJOR CHANGES SINCE 0.39: Modify the DateTimeAsPython output conversion to return None when NULL is output support for Python without threads Ignore additional non-error codes from Sybase (1918 and 11932) Use outputmap in bulkcopy mode (thanks to patch by Cyrille Froehlich) Raise exception when opening a cursor on a closed connection Added unit tests Added new exception DeadLockError when Sybase is in a deadlock situation Add command properties CS_STICKY_BINDS and CS_HAVE_BINDS Added support for inputmap in bulkcopy reuse command and cursor when calling cursor.execute with same request Use ct_setparam to define ct_cursor parameters types instead of ct_param implicit conversion for CS_DATE_TYPE in CS_DATETIME_TYPE DataBuf Adding ct_cmd_props wrapper Increase DataBuf maxlength for params of a request when using CS_CHAR_TYPE params so that the buf can be reused BUGS CORRECTED SINCE 0.39: Corrected money type when using CS_MONEY4 (close bug 2615821) Corrected thread locking in ct_cmd_props (thanks to patch by Cyrille Froehlich) Corrected bug in type mapping in callproc (thanks to report by Skip Montanaro) Correct passing None in a DataBuf (thanks to patch by Bram Kuijvenhoven) The full ChangeLog is here: https://python-sybase.svn.sourceforge.net/svnroot/python-sybase/tags/r0_40pre2/ChangeLog |
From: Francisco D. S. <fra...@ho...> - 2011-10-25 13:19:28
|
From: dikshie <dikshie@gm...> - 2011-08-17 11:57 >Hi, >I got this error message when compile python-sybase with mingw32. > >"-LC:\Program Files\Python27\PCbuild" -lblk -lct -lcs -lpython27 >-lmsvcr90 -o bu ild\lib.win32-2.7\sybasect.pyd >//mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lblk >//mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lct >//mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lcs >collect2: ld returned 1 exit status >error: command 'gcc' failed with exit status 1 >I tried with > syb_libs = ['libblk', 'libct', 'libcs'] >and > syb_libs = ['blk', 'ct', 'cs'] >get same error messages. >I am using python-sybase-0.40pre1.tar.gz on windows xp. Here my quick and dirty hack to build python-sybase-0.40pre1 with mingw32 for Sybase OCS-15_0 and Python 2.7.2 on windows 7 :-) 1) Make mingw the default compiler. In your Python installation directory change in Lib\distutils\ccompiler.py (tuple _default_compilers around line 952) # OS name mappings ('nt', 'mingw32') 2) The sybase library name have changed to avoid possible name conflict, they have a syb prefixe in their name. In python-sybase-0.40 directory change the setup.py file (line 110) syb_libs = ['libsybblk', 'libsybct', 'libsybcs'] 3) Now the compilation work but link fails with unresolved symbol, I must add the sybase dll directory for setup.py to work. I made a dirty change on setup.py, there's probably a better and more elegant solution but it works for me ;-) I added line 124 a new directory variable : syb_dlldir = os.path.join(sybase, 'dll') And I changed near the end (line 267) and added this variable : library_dirs=[syb_libdir, syb_dlldir], Hope that's will help others. Francisco. |
From: dikshie <di...@gm...> - 2011-08-17 11:57:19
|
Hi, I got this error message when compile python-sybase with mingw32. "-LC:\Program Files\Python27\PCbuild" -lblk -lct -lcs -lpython27 -lmsvcr90 -o bu ild\lib.win32-2.7\sybasect.pyd //mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lblk //mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lct //mfauzie1$/personal/mingw/bin/../lib/gcc/mingw32/4.5.2/../../../../mingw32/bin/ld.exe: cannot find -lcs collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 I tried with syb_libs = ['libblk', 'libct', 'libcs'] and syb_libs = ['blk', 'ct', 'cs'] get same error messages. I am using python-sybase-0.40pre1.tar.gz on windows xp. thanks! -- -dikshie- |
From: Michał S. <mi...@sa...> - 2011-02-05 09:57:20
|
Dnia 2011-02-05, sob o godzinie 09:43 +0000, Andrew Lazarev pisze: > Works perfect for me. Don't know why I didn't try it first :\ Hope it > would be useful for you too :) Well I'm stuck with ASA 9 and there's no support for Python there. But I'll definitely try, maybe version 12 of the module will work fine with version 9 server. Thanks for that, -- Michał Sawicz <mi...@sa...> |