python-sybase-misc

Re: [Python-sybase-misc] cursor.close() hangs

[Christophe C. <cc...@fr...>]

Harri Pasanen a écrit :
> On Tuesday 17 July 2007 15:50:00 Christophe Combelles wrote:
>> Christophe Combelles a écrit :
>>> Hello,
>>>
>>> I'm new to this list, and I'm currently trying to access an old
>>> windows Sybase ASA 7.0 from python/linux. I could make it work
>>> with freedts, but it hangs on ...
>>>
> 
> Have you verified the "tds version" in .freetds.conf is correct for 
> that old sybase?

yes I did, and I have tried manny settings.
tds version must be 5.0 for this base

Christophe

> 
> Just a thought,
> 
> Harri
> 
> 
> Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

Re: [Python-sybase-misc] cursor.close() hangs

[Harri P. <har...@tr...>]

T24gVHVlc2RheSAxNyBKdWx5IDIwMDcgMTU6NTA6MDAgQ2hyaXN0b3BoZSBDb21iZWxsZXMgd3Jv
dGU6Cj4gQ2hyaXN0b3BoZSBDb21iZWxsZXMgYSDDqWNyaXQgOgo+ID4gSGVsbG8sCj4gPgo+ID4g
SSdtIG5ldyB0byB0aGlzIGxpc3QsIGFuZCBJJ20gY3VycmVudGx5IHRyeWluZyB0byBhY2Nlc3Mg
YW4gb2xkCj4gPiB3aW5kb3dzIFN5YmFzZSBBU0EgNy4wIGZyb20gcHl0aG9uL2xpbnV4LiBJIGNv
dWxkIG1ha2UgaXQgd29yawo+ID4gd2l0aCBmcmVlZHRzLCBidXQgaXQgaGFuZ3Mgb24gLi4uCj4g
PgoKSGF2ZSB5b3UgdmVyaWZpZWQgdGhlICJ0ZHMgdmVyc2lvbiIgaW4gLmZyZWV0ZHMuY29uZiBp
cyBjb3JyZWN0IGZvciAKdGhhdCBvbGQgc3liYXNlPwoKSnVzdCBhIHRob3VnaHQsCgpIYXJyaQoK
ClByaXZpbGVnZWQgb3IgY29uZmlkZW50aWFsIGluZm9ybWF0aW9uIG1heSBiZSBjb250YWluZWQg
aW4gdGhpcyBtZXNzYWdlLiAgSWYgeW91IGFyZSBub3QgdGhlIGFkZHJlc3NlZSBvZiB0aGlzIG1l
c3NhZ2UgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGJ5IHJldHVybiBhbmQgdGhlcmVhZnRlciBk
ZWxldGUgdGhlIG1lc3NhZ2UsIGFuZCB5b3UgbWF5IG5vdCB1c2UsIGNvcHksIGRpc2Nsb3NlIG9y
IHJlbHkgb24gdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiBpdC4gSW50ZXJuZXQgZS1tYWls
IG1heSBiZSBzdXNjZXB0aWJsZSB0byBkYXRhIGNvcnJ1cHRpb24sIGludGVyY2VwdGlvbiBhbmQg
dW5hdXRob3Jpc2VkIGFtZW5kbWVudCBmb3Igd2hpY2ggV2FsbCBTdHJlZXQgU3lzdGVtcyBkb2Vz
IG5vdCBhY2NlcHQgbGlhYmlsaXR5LiBXaGlsc3Qgd2UgaGF2ZSB0YWtlbiByZWFzb25hYmxlIHBy
ZWNhdXRpb25zIHRvIGVuc3VyZSB0aGF0IHRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMg
aGF2ZSBiZWVuIHN3ZXB0IGZvciB2aXJ1c2VzLCBXYWxsIFN0cmVldCBTeXN0ZW1zIGRvZXMgbm90
IGFjY2VwdCBsaWFiaWxpdHkgZm9yIGFueSBkYW1hZ2Ugc3VzdGFpbmVkIGFzIGEgcmVzdWx0IG9m
IHZpcnVzZXMuICBTdGF0ZW1lbnRzIGluIHRoaXMgbWVzc2FnZSBvciBhdHRhY2htZW50cyB0aGF0
IGRvIG5vdCByZWxhdGUgdG8gdGhlIGJ1c2luZXNzIG9mICBXYWxsIFN0cmVldCBTeXN0ZW1zIGFy
ZSBuZWl0aGVyIGdpdmVuIG5vciBlbmRvcnNlZCBieSB0aGUgY29tcGFueSBvciBpdHMgRGlyZWN0
b3JzLg0KCg==

Re: [Python-sybase-misc] cursor.close() hangs

[Christophe C. <cc...@fr...>]

Christophe Combelles a écrit :
> Christophe Combelles a écrit :
>> Hello,
>>
>> I'm new to this list, and I'm currently trying to access an old windows Sybase 
>> ASA 7.0 from python/linux. I could make it work with freedts, but it hangs on 
>> some operation:
>>
>>  >>> db=Sybase.connect(...)
>>  >>> c=db.cursor()
>>  >>> c.execute('select * from rue')
>>  >>> c.fetchone()
>> (...)
>>  >>> c.close()
>>
>> here it hangs, nothing happens, with 0% CPU.
>> It only exits if I stop the database server:
>>
>> Exception Sybase.DatabaseError: <Sybase.DatabaseError instance at 0xb7cf47cc> in 
>> <bound method _FetchLazy.__del__ of <Sybase._FetchLazy instance at 0xb7cf4e4c>> 
>> ignored
>>
>> What is the recommended way to investigate this?
>> Did anyone have the same problem or is it trivial?
>>
>> thanks,
>> Christophe
> 
> more info:
> I'm using python 2.4.4 with sybase-python 0.38 compiled with -D HAVE_FREETDS -U 
> WANT_BULKCOPY, and freetds/libct4 0.64rc2.
> 
> it also hangs if I call again c.execute(...) after c.fetchone()
> 
> The last thing found in the freetds logfile (debug level 99) is:
> -------------------------------------------------------
> (...)
> token.c:1863:tds_get_data: column 8, type 47, varint size 1
> token.c:1920:processing row.  column size is 16
> token.c:1863:tds_get_data: column 9, type 111, varint size 1
> token.c:1920:processing row.  column size is 8
> token.c:1863:tds_get_data: column 10, type 39, varint size 1
> token.c:1920:processing row.  column size is 3
> token.c:1863:tds_get_data: column 11, type 39, varint size 1
> token.c:1920:processing row.  column size is 1
> token.c:1863:tds_get_data: column 12, type 111, varint size 1
> net.c:446:Received header
> 0000 04 01 00 11 00 00 00 00-                        |........|
> 
> net.c:542:Received packet
> 0000 fd 30 00 02 00 d1 04 00-00                      |.0...... .|
> 
> token.c:1920:processing row.  column size is 253
> 
> -------------------------------------------------------
> 
> If I hit Ctrl-C on the python terminal, the freetds logfile tells:
> 
> net.c:336:socket read interrupted
> (as many times I hit Ctrl-C)
> 
> 
> Is there a clue to say if this is an issue in freetds or python-sybase ?
> 
> -------------------------------------------------------------------------

I have some news:
In fact, the ct_cancel command hangs in _FetchLazy.__del__ of Sybase.py,
when I call cursor.close() after several fetchone()
But this is a random effect, sometimes it hangs, sometimes not.
It might look like a threading issue.

I don't know what the real problem is, but I've tried to replace CS_CANCEL_ALL 
with CS_CANCEL_CURRENT or CS_CANCEL_ATTN, and it don't hangs anymore.

The difference between the different types of cancel is explained here:
http://manuals.sybase.com/onlinebooks/group-cnarc/cng1000e/prgguide/@Generic__BookTextView/5783;pt=6133
But I'm not sure what is the correct one in which circumstances.

regards,
Christophe

Re: [Python-sybase-misc] cursor.close() hangs

[Christophe C. <cc...@fr...>]

Christophe Combelles a écrit :
> Hello,
> 
> I'm new to this list, and I'm currently trying to access an old windows Sybase 
> ASA 7.0 from python/linux. I could make it work with freedts, but it hangs on 
> some operation:
> 
>  >>> db=Sybase.connect(...)
>  >>> c=db.cursor()
>  >>> c.execute('select * from rue')
>  >>> c.fetchone()
> (...)
>  >>> c.close()
> 
> here it hangs, nothing happens, with 0% CPU.
> It only exits if I stop the database server:
> 
> Exception Sybase.DatabaseError: <Sybase.DatabaseError instance at 0xb7cf47cc> in 
> <bound method _FetchLazy.__del__ of <Sybase._FetchLazy instance at 0xb7cf4e4c>> 
> ignored
> 
> What is the recommended way to investigate this?
> Did anyone have the same problem or is it trivial?
> 
> thanks,
> Christophe

more info:
I'm using python 2.4.4 with sybase-python 0.38 compiled with -D HAVE_FREETDS -U 
WANT_BULKCOPY, and freetds/libct4 0.64rc2.

it also hangs if I call again c.execute(...) after c.fetchone()

The last thing found in the freetds logfile (debug level 99) is:
-------------------------------------------------------
(...)
token.c:1863:tds_get_data: column 8, type 47, varint size 1
token.c:1920:processing row.  column size is 16
token.c:1863:tds_get_data: column 9, type 111, varint size 1
token.c:1920:processing row.  column size is 8
token.c:1863:tds_get_data: column 10, type 39, varint size 1
token.c:1920:processing row.  column size is 3
token.c:1863:tds_get_data: column 11, type 39, varint size 1
token.c:1920:processing row.  column size is 1
token.c:1863:tds_get_data: column 12, type 111, varint size 1
net.c:446:Received header
0000 04 01 00 11 00 00 00 00-                        |........|

net.c:542:Received packet
0000 fd 30 00 02 00 d1 04 00-00                      |.0...... .|

token.c:1920:processing row.  column size is 253

-------------------------------------------------------

If I hit Ctrl-C on the python terminal, the freetds logfile tells:

net.c:336:socket read interrupted
(as many times I hit Ctrl-C)


Is there a clue to say if this is an issue in freetds or python-sybase ?

Re: [Python-sybase-misc] list archive broken ?

[Bruno R. <br...@es...>]

Apart from the fact that there is something broken, try this link:
http://sourceforge.net/mailarchive/forum.php?forum_name=python-sybase-misc&max_rows=25&style=nested&viewmonth=200705&viewday=25

Bruno

On 17/07/2007 14:12, Christophe Combelles wrote:
> Is there a problem with the mail archive ?
> 
> I found a message that could be similar to mine, but I cannot access it,
> it leads to an old 2005 message :
> 
> http://sourceforge.net/mailarchive/forum.php?forum_name=python-sybase-misc&viewmonth=200705
> 
> → click on the 'Thread locking bug, look familiar?' message
> → it goes to another message
> 
> 
> Is there another archive somewhere?
> 
> Christophe
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] list archive broken ?

[Christophe C. <cc...@fr...>]

Is there a problem with the mail archive ?

I found a message that could be similar to mine, but I cannot access it,
it leads to an old 2005 message :

http://sourceforge.net/mailarchive/forum.php?forum_name=python-sybase-misc&viewmonth=200705

→ click on the 'Thread locking bug, look familiar?' message
→ it goes to another message


Is there another archive somewhere?

Christophe

[Python-sybase-misc] cursor.close() hangs

[Christophe C. <cc...@fr...>]

Hello,

I'm new to this list, and I'm currently trying to access an old windows Sybase 
ASA 7.0 from python/linux. I could make it work with freedts, but it hangs on 
some operation:

 >>> db=Sybase.connect(...)
 >>> c=db.cursor()
 >>> c.execute('select * from rue')
 >>> c.fetchone()
(...)
 >>> c.close()

here it hangs, nothing happens, with 0% CPU.
It only exits if I stop the database server:

Exception Sybase.DatabaseError: <Sybase.DatabaseError instance at 0xb7cf47cc> in 
<bound method _FetchLazy.__del__ of <Sybase._FetchLazy instance at 0xb7cf4e4c>> 
ignored

What is the recommended way to investigate this?
Did anyone have the same problem or is it trivial?

thanks,
Christophe

[Python-sybase-misc] patch for Sybase.py to allow locale setting

[Harri P. <har...@tr...>]

The attached patched allows setting the locale of the connection to 
match that of the server.   Otherwise you are likely to get the 2403  
warning/error from the Sybase if character sets mismatch in data.

It is implemented as a new keyword argument to Sybase.connect().  
Example usage:

        cnx = Sybase.connect(dbServer, dbUser, dbPasswd,
                             auto_commit=1, datetime = 'python',
                             locale = 'utf8')


Enjoy,

Harri



Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.

[Python-sybase-misc] Character set conversion warning propagated as error

[Harri P. <har...@tr...>]

On Windows I'm getting this:

Sybase.DatabaseError: Msg 2403, Level 10, Line 1 
WARNING!  Some character(s) could not be converted into client's 
character set. 
 Unconverted bytes were changed to question marks ('?').

On Linux I've been a happy user with LC_ALL set to en_US.UTF-8 and 
adding the corresponding line to locales.dat in Sybase OpenClient.

With Windows I haven't found out a way to set the locale from python 
to something that Sybase would be confortable with (basically all the 
accepted codepages appear to be 8 bit?).  But for the moment I'd be 
happy with the question marks, but that gets propaged as hard 
Sybase.DatabaseError.  

Any Hints?

Harri


Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.

Re: [Python-sybase-misc] Thread locking bug, look familiar?

[<sa...@po...>]

Hi Harry,

I run python-sybase 0.38 with Python 2.5.1 on a linux system (not 64 
bits however) and I don't have any problem.

Have you run the test suite on your system and is there any failure? 
Otherwise could you write a small unitary test to illustrate the problem?


regards

--
Sébastien Sablé


Harri Pasanen a écrit :
> Hmm... actually it seems this is surfacing on Python 2.5.1, but on 
> Python 2.5 it works.  And the same problem seems to affect Linux 
> (RedHat, 64 bit).  
> 
> Has anyone use python-sybase-0.38 with Python 2.5.1?   
> 
> It is possible that my problem comes from something else, but so far 
> only difference I'm aware of is the python version.  
> 
> 
> 
> -Harri

Re: [Python-sybase-misc] 0.38 equivalent of MySQLdb's converters dictionary?

[<sa...@po...>]

Hi Skip,

there is no new way to do what you would like in 0.38. However it is 
clearly something which would be very useful.

There is an ongoing thread on the db-sig list concerning this subject:
http://mail.python.org/pipermail/db-sig/2007-April/004944.html
it would be great if a standardized way to handle this could be added to 
the DBAPI.

Also could you send me the source of your modified version so that I can 
  see if it can be merged/adapted?

regards

--
Sébastien Sablé


Skip Montanaro a écrit :
> MySQLdb allows the user to control mapping between Python types and Sybase
> types on-the-fly using a converters argument to the connection constructor.
> We need this sort of functionality at work to support some legacy Python
> apps which expect dates to be represented in Unix epoch time, e.g.:
> 
>     conn = Connection(converters={DateTimeType: _dt_as_float})
> 
> I implemented this in python-sybase 0.36 but would like to stop maintaining
> my own forked version of the module.  Is there some way to control this
> mapping on a case-by-case basis in 0.38pre1?
> 
> Thx,
> 
> --
> Skip Montanaro - sk...@po... - http://www.webfast.com/~skip/
> "The hippies and the hipsters did some great stuff in the sixties,
> but the geeks pulled their weight too." -- Billy Bragg

[Python-sybase-misc] 0.38 equivalent of MySQLdb's converters dictionary?

[Skip M. <ski...@gm...>]

MySQLdb allows the user to control mapping between Python types and Sybase
types on-the-fly using a converters argument to the connection constructor.
We need this sort of functionality at work to support some legacy Python
apps which expect dates to be represented in Unix epoch time, e.g.:

    conn = Connection(converters={DateTimeType: _dt_as_float})

I implemented this in python-sybase 0.36 but would like to stop maintaining
my own forked version of the module.  Is there some way to control this
mapping on a case-by-case basis in 0.38pre1?

Thx,

--
Skip Montanaro - sk...@po... - http://www.webfast.com/~skip/
"The hippies and the hipsters did some great stuff in the sixties,
but the geeks pulled their weight too." -- Billy Bragg

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Python-sybase-misc mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

Re: [Python-sybase-misc] Thread locking bug, look familiar?

[Harri P. <har...@tr...>]

SSByZXByb2R1Y2VkIHRoZSBwcm9ibGVtIHdpdGggdGhlIGZvbGxvd2luZyB0ZXN0IHNjcmlwdDoK
Ci0tLS04PC0tLS0tLS0tODwtLS0tLS0tLS0tLS0tODwtLS0tLS0tLTg8LS0tLS0tLS0tLS0tLTg8
LS0tLS0tLS04PC0tLS0tLS0tLQpmcm9tIG9wdHBhcnNlIGltcG9ydCBPcHRpb25QYXJzZXIKcGFy
c2VyID0gT3B0aW9uUGFyc2VyKCkKCnBhcnNlci5hZGRfb3B0aW9uKCItRCIsIGRlc3Q9ImRiTmFt
ZSIsIAogICAgICAgICAgICAgICAgICBoZWxwPSJEYXRhYmFzZSB0byBjb25uZWN0IHRvIikKcGFy
c2VyLmFkZF9vcHRpb24oIi1TIiwgZGVzdD0iZGJTZXJ2ZXIiLCAKICAgICAgICAgICAgICAgICAg
aGVscD0iRGF0YWJhc2Ugc2VydmVyIHRvIHVzZSIpCnBhcnNlci5hZGRfb3B0aW9uKCItVSIsIGRl
c3Q9ImRiVXNlciIsIAogICAgICAgICAgICAgICAgICBoZWxwPSJEYXRhYmFzZSB1c2VyIikKcGFy
c2VyLmFkZF9vcHRpb24oIi1QIiwgZGVzdD0iZGJQYXNzd2QiLCAKICAgICAgICAgICAgICAgICAg
aGVscD0iRGF0YWJhc2UgdXNlciBwYXNzd29yZCIpCihvcHRpb25zLCBhcmdzKSA9IHBhcnNlci5w
YXJzZV9hcmdzKCkKCgppbXBvcnQgU3liYXNlCgpjbnggPSBTeWJhc2UuY29ubmVjdChvcHRpb25z
LmRiU2VydmVyLCBvcHRpb25zLmRiVXNlciwKICAgICAgICAgICAgICAgICAgICAgb3B0aW9ucy5k
YlBhc3N3ZCwgYXV0b19jb21taXQ9MSkKCnF1ZXJ5ID0gInNlbGVjdCB0MT1vYmplY3RfbmFtZShp
bnN0cmlnKSwgdDI9b2JqZWN0X25hbWUodXBkdHJpZyksIAp0Mz1vYmplY3RfbmFtZShkZWx0cmln
KSBmcm9tIHN5c29iamVjdHMgd2hlcmUgCmlkPW9iamVjdF9pZCgnQWNjb3VudCcpIgoKY3Vyc29y
ID0gY254LmN1cnNvcigpCmN1cnNvci5leGVjdXRlKCJ1c2UgIitvcHRpb25zLmRiTmFtZSkKY3Vy
c29yLmV4ZWN1dGUocXVlcnkpCnRyaWdnZXJzID0gY3Vyc29yLmZldGNoYWxsKCkKd2hpbGUgY3Vy
c29yLm5leHRzZXQoKToKICAgIGR1bW15ID0gY3Vyc29yLmZldGNoYWxsKCkKCgotLS0tLS0tLS0t
ODwtLS0tLS0tLTg8LS0tLS0tLS0tLS0tLTg8LS0tLS0tLS04PC0tLS0tLS0tLS0tLS04PC0tLS0t
LS0tODwtLS0tLS0tLS0KCllvdSBjYW4gc3VidGl0dXRlIHByb2JhYmx5IGFueSB0YWJsZSBuYW1l
IGZvciB0aGUgJ0FjY291bnQnIGFib3ZlLgpXb3VsZCB5b3UgbGlrZSBtZSB0byBjcmVhdGUgYSB0
cmFjIGl0ZW0gYXQgc291cmNlZm9yZ2UgZm9yIHRoaXM/CgpDaGVlcnMsCgpIYXJyaQoKCgpPbiBX
ZWRuZXNkYXkgMTYgTWF5IDIwMDcgMTQ6MTQ6MzQgU8OpYmFzdGllbiBTYWJsw6kgd3JvdGU6Cj4g
SGkgSGFycnksCj4KPiBJIHJ1biBweXRob24tc3liYXNlIDAuMzggd2l0aCBQeXRob24gMi41LjEg
b24gYSBsaW51eCBzeXN0ZW0gKG5vdAo+IDY0IGJpdHMgaG93ZXZlcikgYW5kIEkgZG9uJ3QgaGF2
ZSBhbnkgcHJvYmxlbS4KPgo+IEhhdmUgeW91IHJ1biB0aGUgdGVzdCBzdWl0ZSBvbiB5b3VyIHN5
c3RlbSBhbmQgaXMgdGhlcmUgYW55Cj4gZmFpbHVyZT8gT3RoZXJ3aXNlIGNvdWxkIHlvdSB3cml0
ZSBhIHNtYWxsIHVuaXRhcnkgdGVzdCB0bwo+IGlsbHVzdHJhdGUgdGhlIHByb2JsZW0/Cj4KPgo+
IHJlZ2FyZHMKPgo+IC0tCj4gU8OpYmFzdGllbiBTYWJsw6kKPgo+IEhhcnJpIFBhc2FuZW4gYSDD
qWNyaXQgOgo+ID4gSG1tLi4uIGFjdHVhbGx5IGl0IHNlZW1zIHRoaXMgaXMgc3VyZmFjaW5nIG9u
IFB5dGhvbiAyLjUuMSwgYnV0Cj4gPiBvbiBQeXRob24gMi41IGl0IHdvcmtzLiAgQW5kIHRoZSBz
YW1lIHByb2JsZW0gc2VlbXMgdG8gYWZmZWN0Cj4gPiBMaW51eCAoUmVkSGF0LCA2NCBiaXQpLgo+
ID4KPiA+IEhhcyBhbnlvbmUgdXNlIHB5dGhvbi1zeWJhc2UtMC4zOCB3aXRoIFB5dGhvbiAyLjUu
MT8KPiA+Cj4gPiBJdCBpcyBwb3NzaWJsZSB0aGF0IG15IHByb2JsZW0gY29tZXMgZnJvbSBzb21l
dGhpbmcgZWxzZSwgYnV0IHNvCj4gPiBmYXIgb25seSBkaWZmZXJlbmNlIEknbSBhd2FyZSBvZiBp
cyB0aGUgcHl0aG9uIHZlcnNpb24uCj4gPgo+ID4KPiA+Cj4gPiAtSGFycmkKCgpQcml2aWxlZ2Vk
IG9yIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBtYXkgYmUgY29udGFpbmVkIGluIHRoaXMgbWVz
c2FnZS4gIElmIHlvdSBhcmUgbm90IHRoZSBhZGRyZXNzZWUgb2YgdGhpcyBtZXNzYWdlIHBsZWFz
ZSBub3RpZnkgdGhlIHNlbmRlciBieSByZXR1cm4gYW5kIHRoZXJlYWZ0ZXIgZGVsZXRlIHRoZSBt
ZXNzYWdlLCBhbmQgeW91IG1heSBub3QgdXNlLCBjb3B5LCBkaXNjbG9zZSBvciByZWx5IG9uIHRo
ZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaW4gaXQuIEludGVybmV0IGUtbWFpbCBtYXkgYmUgc3Vz
Y2VwdGlibGUgdG8gZGF0YSBjb3JydXB0aW9uLCBpbnRlcmNlcHRpb24gYW5kIHVuYXV0aG9yaXNl
ZCBhbWVuZG1lbnQgZm9yIHdoaWNoIFdhbGwgU3RyZWV0IFN5c3RlbXMgZG9lcyBub3QgYWNjZXB0
IGxpYWJpbGl0eS4gV2hpbHN0IHdlIGhhdmUgdGFrZW4gcmVhc29uYWJsZSBwcmVjYXV0aW9ucyB0
byBlbnN1cmUgdGhhdCB0aGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGhhdmUgYmVlbiBz
d2VwdCBmb3IgdmlydXNlcywgV2FsbCBTdHJlZXQgU3lzdGVtcyBkb2VzIG5vdCBhY2NlcHQgbGlh
YmlsaXR5IGZvciBhbnkgZGFtYWdlIHN1c3RhaW5lZCBhcyBhIHJlc3VsdCBvZiB2aXJ1c2VzLiAg
U3RhdGVtZW50cyBpbiB0aGlzIG1lc3NhZ2Ugb3IgYXR0YWNobWVudHMgdGhhdCBkbyBub3QgcmVs
YXRlIHRvIHRoZSBidXNpbmVzcyBvZiAgV2FsbCBTdHJlZXQgU3lzdGVtcyBhcmUgbmVpdGhlciBn
aXZlbiBub3IgZW5kb3JzZWQgYnkgdGhlIGNvbXBhbnkgb3IgaXRzIERpcmVjdG9ycy4NCgotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tClRoaXMgU0YubmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieSBEQjIgRXhwcmVz
cwpEb3dubG9hZCBEQjIgRXhwcmVzcyBDIC0gdGhlIEZSRUUgdmVyc2lvbiBvZiBEQjIgZXhwcmVz
cyBhbmQgdGFrZQpjb250cm9sIG9mIHlvdXIgWE1MLiBObyBsaW1pdHMuIEp1c3QgZGF0YS4gQ2xp
Y2sgdG8gZ2V0IGl0IG5vdy4KaHR0cDovL3NvdXJjZWZvcmdlLm5ldC9wb3dlcmJhci9kYjIvCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fClB5dGhvbi1zeWJh
c2UtbWlzYyBtYWlsaW5nIGxpc3QKUHl0aG9uLXN5YmFzZS1taXNjQGxpc3RzLnNvdXJjZWZvcmdl
Lm5ldApodHRwczovL2xpc3RzLnNvdXJjZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9weXRob24t
c3liYXNlLW1pc2MK

Re: [Python-sybase-misc] Thread locking bug, look familiar?

[Harri P. <har...@tr...>]

U29tZSBvdGhlciBvYnNlcnZhdGlvbnM6CgpJbiBteSBsb2NhbCBjb3B5IG9uIExpbnV4IDMyIGJp
dCBJJ3ZlIG1vZGlmaWVkIHRoZSBzeWJhc2UgbGlicyBpbiAKc2V0dXAucHkgdG8gcmVhZDoKCiAg
ICBpZiBvcy51bmFtZSgpWzBdID09ICdMaW51eCc6CiAgICAgICAgbGliX25hbWVzID0gWydibGtf
cicsICdjdF9yJywgJ2NzX3InLCAnc3lidGNsX3InLCAnaW5zY2tfcicsCiAgICAgICAgICAgICAg
ICAgICAgICdjb21uX3InLCAnaW50bF9yJ10KCk9uIG15IG1hY2hpbmUgSSBoYXZlIFN5YmFzZSAx
Mi41LjAgT3BlbkNsaWVudC4KCkkgYmVsaWV2ZSB0aGlzIGlzIG5lY2Vzc2FyeSBmb3IgdGhlIHRo
cmVhZCBzYWZldHkgdG8gYmUgYXNzdXJlZC4gIEl0IAphbHNvIG5pY2VseSBzb2x2ZXMgdGhlIGNv
bmZsaWN0IHdpdGggL3Vzci9saWIvbGliaW50bC5zbywgd2hpY2ggY29tZXMgCmZyb20gZ2V0dGV4
dC1kZXZlbDoKCgpbaGFycmlAZGVsbC1oYXJyaSBkYmNoZWNrZXJdJCBycG0gLXFpZiAvdXNyL2xp
Yi9saWJpbnRsLnNvCk5hbWUgICAgICAgIDogZ2V0dGV4dC1kZXZlbCAgICAgICAgICAgICAgICBS
ZWxvY2F0aW9uczogKG5vdCAKcmVsb2NhdGFibGUpClZlcnNpb24gICAgIDogMC4xNi4xICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFZlbmRvcjogTWFuZHJpdmEKCgpBcyB0byB0aGUgcHJvYmxl
bSBhbmQgaGFuZCwgSSBzdGFydGVkIHRvIGNyZWF0ZSBhIHN0YW5kYWxvbmUgdGVzdGNhc2UsIAph
bmQgbm90aWNlZCB0aGF0IHB5dGhvbiB2ZXJzaW9uIGRvZXMgbm90IG1hdHRlciwgSSdtIGdldHRp
bmcgdGhlIApmb2xsb3dpbmcgYm90aCB3aXRoIDIuNSBhbmQgMi41LjE6CgogIEZpbGUgIi91c3Iv
bGliL3B5dGhvbjIuNS9zaXRlLXBhY2thZ2VzL1N5YmFzZS5weSIsIGxpbmUgODM3LCBpbiAKbmV4
dHNldAogICAgZGVzYyA9IHNlbGYuX2ZldGNoZXIubmV4dHNldCgpCiAgRmlsZSAiL3Vzci9saWIv
cHl0aG9uMi41L3NpdGUtcGFja2FnZXMvU3liYXNlLnB5IiwgbGluZSA2MjcsIGluIApuZXh0c2V0
CiAgICBzZWxmLl91bmxvY2soKQogIEZpbGUgIi91c3IvbGliL3B5dGhvbjIuNS9zaXRlLXBhY2th
Z2VzL1N5YmFzZS5weSIsIGxpbmUgNDY2LCBpbiAKX3VubG9jawogICAgc2VsZi5fb3duZXIuX3Vu
bG9jaygpCiAgRmlsZSAiL3Vzci9saWIvcHl0aG9uMi41L3NpdGUtcGFja2FnZXMvU3liYXNlLnB5
IiwgbGluZSA5OTYsIGluIApfdW5sb2NrCiAgICBzZWxmLl9jb25ubG9jay5yZWxlYXNlKCkKICBG
aWxlICIvdXNyL2xpYi9weXRob24yLjUvdGhyZWFkaW5nLnB5IiwgbGluZSAxMTUsIGluIHJlbGVh
c2UKICAgIGFzc2VydCBzZWxmLl9fb3duZXIgaXMgbWUsICJyZWxlYXNlKCkgb2YgdW4tYWNxdWly
ZSgpZCBsb2NrIgpBc3NlcnRpb25FcnJvcjogcmVsZWFzZSgpIG9mIHVuLWFjcXVpcmUoKWQgbG9j
awpFeGNlcHRpb24gdGhyZWFkLmVycm9yOiAncmVsZWFzZSB1bmxvY2tlZCBsb2NrJyBpbiA8Ym91
bmQgbWV0aG9kIApfRmV0Y2hMYXp5Ll9fZGVsX18gb2YgPFN5YmFzZS5fRmV0Y2hMYXp5IGluc3Rh
bmNlIGF0IDB4Yjc5ZmQxNmM+PiAKaWdub3JlZAoKSSdsbCBjb250aW51ZSBodW50aW5nLi4uIGtl
ZXAgeW91IHBvc3RlZC4KCi1IYXJyaQoKCk9uIFdlZG5lc2RheSAxNiBNYXkgMjAwNyAxNDoxNDoz
NCBTw6liYXN0aWVuIFNhYmzDqSB3cm90ZToKPiBIaSBIYXJyeSwKPgo+IEkgcnVuIHB5dGhvbi1z
eWJhc2UgMC4zOCB3aXRoIFB5dGhvbiAyLjUuMSBvbiBhIGxpbnV4IHN5c3RlbSAobm90Cj4gNjQg
Yml0cyBob3dldmVyKSBhbmQgSSBkb24ndCBoYXZlIGFueSBwcm9ibGVtLgo+Cj4gSGF2ZSB5b3Ug
cnVuIHRoZSB0ZXN0IHN1aXRlIG9uIHlvdXIgc3lzdGVtIGFuZCBpcyB0aGVyZSBhbnkKPiBmYWls
dXJlPyBPdGhlcndpc2UgY291bGQgeW91IHdyaXRlIGEgc21hbGwgdW5pdGFyeSB0ZXN0IHRvCj4g
aWxsdXN0cmF0ZSB0aGUgcHJvYmxlbT8KPgo+Cj4gcmVnYXJkcwo+Cj4gLS0KPiBTw6liYXN0aWVu
IFNhYmzDqQo+Cj4gSGFycmkgUGFzYW5lbiBhIMOpY3JpdCA6Cj4gPiBIbW0uLi4gYWN0dWFsbHkg
aXQgc2VlbXMgdGhpcyBpcyBzdXJmYWNpbmcgb24gUHl0aG9uIDIuNS4xLCBidXQKPiA+IG9uIFB5
dGhvbiAyLjUgaXQgd29ya3MuICBBbmQgdGhlIHNhbWUgcHJvYmxlbSBzZWVtcyB0byBhZmZlY3QK
PiA+IExpbnV4IChSZWRIYXQsIDY0IGJpdCkuCj4gPgo+ID4gSGFzIGFueW9uZSB1c2UgcHl0aG9u
LXN5YmFzZS0wLjM4IHdpdGggUHl0aG9uIDIuNS4xPwo+ID4KPiA+IEl0IGlzIHBvc3NpYmxlIHRo
YXQgbXkgcHJvYmxlbSBjb21lcyBmcm9tIHNvbWV0aGluZyBlbHNlLCBidXQgc28KPiA+IGZhciBv
bmx5IGRpZmZlcmVuY2UgSSdtIGF3YXJlIG9mIGlzIHRoZSBweXRob24gdmVyc2lvbi4KPiA+Cj4g
Pgo+ID4KPiA+IC1IYXJyaQoKClByaXZpbGVnZWQgb3IgY29uZmlkZW50aWFsIGluZm9ybWF0aW9u
IG1heSBiZSBjb250YWluZWQgaW4gdGhpcyBtZXNzYWdlLiAgSWYgeW91IGFyZSBub3QgdGhlIGFk
ZHJlc3NlZSBvZiB0aGlzIG1lc3NhZ2UgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGJ5IHJldHVy
biBhbmQgdGhlcmVhZnRlciBkZWxldGUgdGhlIG1lc3NhZ2UsIGFuZCB5b3UgbWF5IG5vdCB1c2Us
IGNvcHksIGRpc2Nsb3NlIG9yIHJlbHkgb24gdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBpbiBp
dC4gSW50ZXJuZXQgZS1tYWlsIG1heSBiZSBzdXNjZXB0aWJsZSB0byBkYXRhIGNvcnJ1cHRpb24s
IGludGVyY2VwdGlvbiBhbmQgdW5hdXRob3Jpc2VkIGFtZW5kbWVudCBmb3Igd2hpY2ggV2FsbCBT
dHJlZXQgU3lzdGVtcyBkb2VzIG5vdCBhY2NlcHQgbGlhYmlsaXR5LiBXaGlsc3Qgd2UgaGF2ZSB0
YWtlbiByZWFzb25hYmxlIHByZWNhdXRpb25zIHRvIGVuc3VyZSB0aGF0IHRoaXMgZS1tYWlsIGFu
ZCBhbnkgYXR0YWNobWVudHMgaGF2ZSBiZWVuIHN3ZXB0IGZvciB2aXJ1c2VzLCBXYWxsIFN0cmVl
dCBTeXN0ZW1zIGRvZXMgbm90IGFjY2VwdCBsaWFiaWxpdHkgZm9yIGFueSBkYW1hZ2Ugc3VzdGFp
bmVkIGFzIGEgcmVzdWx0IG9mIHZpcnVzZXMuICBTdGF0ZW1lbnRzIGluIHRoaXMgbWVzc2FnZSBv
ciBhdHRhY2htZW50cyB0aGF0IGRvIG5vdCByZWxhdGUgdG8gdGhlIGJ1c2luZXNzIG9mICBXYWxs
IFN0cmVldCBTeXN0ZW1zIGFyZSBuZWl0aGVyIGdpdmVuIG5vciBlbmRvcnNlZCBieSB0aGUgY29t
cGFueSBvciBpdHMgRGlyZWN0b3JzLg0KCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVGhpcyBTRi5uZXQgZW1h
aWwgaXMgc3BvbnNvcmVkIGJ5IERCMiBFeHByZXNzCkRvd25sb2FkIERCMiBFeHByZXNzIEMgLSB0
aGUgRlJFRSB2ZXJzaW9uIG9mIERCMiBleHByZXNzIGFuZCB0YWtlCmNvbnRyb2wgb2YgeW91ciBY
TUwuIE5vIGxpbWl0cy4gSnVzdCBkYXRhLiBDbGljayB0byBnZXQgaXQgbm93LgpodHRwOi8vc291
cmNlZm9yZ2UubmV0L3Bvd2VyYmFyL2RiMi8KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KUHl0aG9uLXN5YmFzZS1taXNjIG1haWxpbmcgbGlzdApQeXRob24t
c3liYXNlLW1pc2NAbGlzdHMuc291cmNlZm9yZ2UubmV0Cmh0dHBzOi8vbGlzdHMuc291cmNlZm9y
Z2UubmV0L2xpc3RzL2xpc3RpbmZvL3B5dGhvbi1zeWJhc2UtbWlzYwo=

Re: [Python-sybase-misc] Thread locking bug, look familiar?

[Harri P. <har...@wa...>]

Hmm... actually it seems this is surfacing on Python 2.5.1, but on 
Python 2.5 it works.  And the same problem seems to affect Linux 
(RedHat, 64 bit).  

Has anyone use python-sybase-0.38 with Python 2.5.1?   

It is possible that my problem comes from something else, but so far 
only difference I'm aware of is the python version.  



-Harri


On Tuesday 15 May 2007 17:49:52 Harri Pasanen wrote:
> I'm getting this with Python 2.5 on Windows, Sybase module 0.38
>
>     while c.nextset():
>   File "..\site-packages\Sybase.py", line 837, in nextset
>     desc = self._fetcher.nextset()
>   File "..\site-packages\Sybase.py", line 627, in nextset
>     self._unlock()
>   File "..\site-packages\Sybase.py", line 466, in _unlock
>     self._owner._unlock()
>   File "..\site-packages\Sybase.py", line 996, in _unlock
>     self._connlock.release()
>   File "..\lib\threading.py", line 1
> 15, in release
>     assert self.__owner is me, "release() of un-acquire()d lock"
> AssertionError: release() of un-acquire()d lock
> Exception thread.error: 'release unlocked lock' in <bound method
> _FetchLazy.__del__ of <Sybase._FetchLazy instance at 0x00A02AD0>>
> ignored
>
> I wonder if it looks familiar to anyone?
>
> -Harri
>
>
>
> Privileged or confidential information may be contained in this
> message.  If you are not the addressee of this message please
> notify the sender by return and thereafter delete the message, and
> you may not use, copy, disclose or rely on the information
> contained in it. Internet e-mail may be susceptible to data
> corruption, interception and unauthorised amendment for which Wall
> Street Systems does not accept liability. Whilst we have taken
> reasonable precautions to ensure that this e-mail and any
> attachments have been swept for viruses, Wall Street Systems does
> not accept liability for any damage sustained as a result of
> viruses.  Statements in this message or attachments that do not
> relate to the business of  Wall Street Systems are neither given
> nor endorsed by the company or its Directors.
>
>
> -------------------------------------------------------------------
>------ This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc




Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Python-sybase-misc mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] Thread locking bug, look familiar?

[Harri P. <har...@tr...>]

I'm getting this with Python 2.5 on Windows, Sybase module 0.38

    while c.nextset(): 
  File "..\site-packages\Sybase.py", line 837, in nextset 
    desc = self._fetcher.nextset() 
  File "..\site-packages\Sybase.py", line 627, in nextset 
    self._unlock()
  File "..\site-packages\Sybase.py", line 466, in _unlock 
    self._owner._unlock() 
  File "..\site-packages\Sybase.py", line 996, in _unlock 
    self._connlock.release() 
  File "..\lib\threading.py", line 1 
15, in release 
    assert self.__owner is me, "release() of un-acquire()d lock" 
AssertionError: release() of un-acquire()d lock 
Exception thread.error: 'release unlocked lock' in <bound method 
_FetchLazy.__del__ of <Sybase._FetchLazy instance at 0x00A02AD0>> 
ignored 

I wonder if it looks familiar to anyone?

-Harri
 


Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Python-sybase-misc mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] Sybase module 0.38 released

[<sa...@us...>]

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.38.tar.gz

The module home page is here:

http://python-sybase.sourceforge.net/


CHANGES SINCE 0.38pre2:

* Corrected bug in databuf_alloc: Sybase reports the wrong maxlength
for numeric type - verified with Sybase 12.5 - thanks to patch
provided by Phil Porter


MAJOR CHANGES SINCE 0.37:

* This release works with python 2.5

* It also works with sybase 15

* It works with 64bits clients

* It can be configured to return native python datetime objects

* The bug "This routine cannot be called because another command
structure has results pending." which appears in various cases has
been corrected

* It includes a unitary test suite based on the dbapi2.0 compliance
test suite

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Python-sybase-misc mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] Testing mailing list archive

[<sa...@us...>]

This is a test message to see if the mailing list archive is correctly 
updated at this url:

http://sourceforge.net/mailarchive/forum.php?forum_name=python-sybase-misc

New messages were not archived since the migration of the mailing list 
to sourceforge. This should now be solved.

https://sourceforge.net/tracker/?func=detail&atid=200001&aid=1721473&group_id=1

regards

--
Sébastien Sablé

Re: [python-sybase] SQLAlchemy

[<sk...@po...>]

    >> Has anyone looked at what it would take to make SQLAlchemy, to work
    >> with Sybase?

    Harri> I believe someone already asked this, but I'm not sure if there
    Harri> were any replies?

I did.  There weren't any.

Skip

[python-sybase] SQLAlchemy

[Harri P. <har...@tr...>]

Has anyone looked at what it would take to make SQLAlchemy, 
( http://www.sqlalchemy.org/  ) to work with Sybase?

I believe someone already asked this, but I'm not sure if there were 
any replies?

-Harri


Privileged or confidential information may be contained in this message.  If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Wall Street Systems does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Wall Street Systems does not accept liability for any damage sustained as a result of viruses.  Statements in this message or attachments that do not relate to the business of  Wall Street Systems are neither given nor endorsed by the company or its Directors.

Re: [python-sybase] Build runs into problems with sybasect extension

[<sa...@po...>]

Hi John,

I don't have a windows environment to test python-sybase for the moment. 
I will try to install that in coming weeks.

The following line in your log looks suspicious:
 > -llibblk -llibct -llibcs -lpython25 -lmsvcr71 -o

It should probably be something like:
 > -lblk -lct -lcs -lpython25 -lmsvcr71 -o

you should modify the setup.py file - line 76:

     syb_libs = ['libblk', 'libct', 'libcs']
into:
     syb_libs = ['blk', 'ct', 'cs']

I suppose the script was made for compilation with visual studio rather 
than mingw32?

I should be able to provide a clean fix when I will have a windows 
environment with sybase.

regards

--
Sébastien Sablé

[python-sybase] Build runs into problems with sybasect extension

[John C. <jo...@al...>]

Hi Folks,

I'm sure this is just some kind of simple thing, but I am not an 
experienced gcc user and I am quite unsure how to proceed. I'm trying to 
build on Win XP. I've had to tell it to use the cygwin compiler and that 
works, to a point. I do not have the mxDateTime package mentioned in the 
"Prerequisites" section, but it appears that is not absolutely necessary 
(and since I don't need to manipulate datetime values at the moment, I 
was hoping it wouldn't matter).

Do I need the Sybase header files in some include directory (other than 
the one they're in under the Sybase install)? The SYBASE & SYBASE_OCS 
environment variables are properly set.

Any suggestions welcomed. Output of the compiler follows.

John


A bunch of stuff has been built successfully. Using this command:

setup.py build -c mingw32

But, when it gets to this point, I get pages of errors (similar ones are 
omitted and I've put in ... )--some the line-breaks have been changed 
for clarity:

building 'sybasect' extension
writing build\temp.win32-2.5\Release\sybasect.def
C:\cygwin\bin\gcc.exe -mno-cygwin -shared -s 
build\temp.win32-2.5\Release\blk.o
build\temp.win32-2.5\Release\databuf.o build\temp.win32-2.5\Release\cmd.o
 build\temp.win32-2.5\Release\conn.o build\temp.win32-2.5\Release\ctx.o 
build\temp.win32-2.5\Release\datafmt.o
 build\temp.win32-2.5\Release\iodesc.o build\temp.win32-2.5\Release\locale.o
 build\temp.win32-2.5\Release\msgs.o build\temp.win32-2.5\Release\numeric.o
 build\temp.win32-2.5\Release\money.o 
build\temp.win32-2.5\Release\datetime.o
 build\temp.win32-2.5\Release\sybasect.o 
build\temp.win32-2.5\Release\sybasect.def
 -LC:\SybaseClient125\OCS-12_5\lib -LC:\Python25\libs -LC:\Python25\PCBuild
 -llibblk -llibct -llibcs -lpython25 -lmsvcr71 -o 
build\lib.win32-2.5\sybasect.pyd
build\temp.win32-2.5\Release\blk.o:blk.c:(.text+0xa0): undefined 
reference to `_blk_bind'
build\temp.win32-2.5\Release\blk.o:blk.c:(.text+0x1da): undefined 
reference to `_blk_describe'
...
    There's dozens of errors that mention various _blk and _cs routines
...
build\temp.win32-2.5\Release\locale.o:locale.c:(.text+0x66): undefined 
reference to `_cs_loc_alloc'
build\temp.win32-2.5\Release\locale.o:locale.c:(.text+0x178): undefined 
reference to `_cs_loc_drop'
...
build\temp.win32-2.5\Release\numeric.o:numeric.c:(.text+0x78): undefined 
reference to `_cs_convert'
build\temp.win32-2.5\Release\numeric.o:numeric.c:(.text+0x15b): 
undefined reference to `_cs_convert'
...
build\temp.win32-2.5\Release\money.o:money.c:(.text+0x70): undefined 
reference to `_cs_convert'
build\temp.win32-2.5\Release\money.o:money.c:(.text+0x151): undefined 
reference to `_cs_convert'
...
build\temp.win32-2.5\Release\datetime.o:datetime.c:(.text+0x3a): 
undefined reference to `_cs_dt_crack'
build\temp.win32-2.5\Release\datetime.o:datetime.c:(.text+0x59): 
undefined reference to `_cs_dt_crack'
collect2: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

[python-sybase] Sybase module 0.38pre2 released

[<sa...@us...>]

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.38pre2.tar.gz

The module home page is here:

http://python-sybase.sourceforge.net/


CHANGES SINCE 0.38pre1:

* Add structured error information to Sybase.DatabaseError thanks to
patch provided by Gregory Bond (close tracker 1631902)

* Resurrected Sybase.Bulkcopy functionality thanks to patch provided
by Gregory Bond (close tracker 1632916)

* Corrected AttributeError when locking is off (close tracker 1637942
reported by Jim Nusbaum)

* Corrected incorrect type mx.DateTime.DateTime returned by
Sybase.Date() in "mx" datetime mode. This type is not supported by
DataBuf.

* Corrected crash on a BLK object when debug is enabled (close tracker
1630941 reported by Gregory Bond)

* rowcount is now propagated to Cursor (corrects tracker 1621003)

* Added support for python datetime type in DataBuf and as parameter
of Cursor.execute()

* Corrected Date, Time and Timestamp functions when using mx.DateTime
or native python datetime types

* Corrected DATETIME as cursor.description still returns native Sybase
datetime types

* Corrected blk_describe always returns (status, None) thanks to patch
by Phil Porter

* Patch to handle CS_LONG type based on	patch by Paul Rensing


MAJOR CHANGES SINCE 0.37:

* This release works with python 2.5

* It also works with sybase 15

* It works with 64bits clients

* It can be configured to return native python datetime objects

* The bug "This routine cannot be called because another command
structure has results pending." which appears in various cases has
been corrected

* It includes a unitary test suite based on the dbapi2.0 compliance
test suite

Re: [python-sybase] Patch: Resurrect Sybase.Bulkcopy

[<sa...@us...>]

Hi Gregory,

thank you for your patch; I will review it, write some unitary tests and 
integrate it in a coming version.

regards

--
Sébastien Sablé

Gregory Bond a écrit :
> I’ve just uploaded to sourceforge a patch to resurrect the high-level 
> Bulkcopy() functionality.  It’s working for me but I’ve not thoroughly 
> debugged all the corner cases (especially thread locking).  Docs have 
> been updated but I can’t regenerate the HTML.
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=1632916&group_id=184050&atid=907703 
> <http://sourceforge.net/tracker/index.php?func=detail&aid=1632916&group_id=184050&atid=907703>
> 
> Let me know if you have any comments.
> 
> Greg.

[python-sybase] Patch: Resurrect Sybase.Bulkcopy

[Gregory B. <gn...@it...>]

I=B9ve just uploaded to sourceforge a patch to resurrect the high-level
Bulkcopy() functionality.  It=B9s working for me but I=B9ve not thoroughly
debugged all the corner cases (especially thread locking).  Docs have been
updated but I can=B9t regenerate the HTML.

http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1632916&group_id=3D1=
8
4050&atid=3D907703

Let me know if you have any comments.

Greg.