"Dittmar, Daniel" <[EMAIL PROTECTED]> schrieb am 06.11.02 19:03:15:
> There exists an experimental version of the Python interface that
> ...
Hello Daniel,
it seems, that the following construction does (again) return the
shown traceback, when no resulting rows are found.
(I found BTW, that the error messages are not found, must
check that)
# code example:
from sapdb import sapdb
print sapdb._buildInfo()
session = sapdb.connect(username, pwd, dbname, hostname)
# SQL statement, that returns no rows.
sql = "select testarea from event where testarea like '*a' "
for row in session.sql(sql):
print row
# Output:
sapdbpy 7.3.0 Build 030-111-000-000
Traceback (most recent call last):
File "test1.py", line 9, in ?
for row in session.sql(sql):
sapdb.SQLError: sapdb.SQLError: [100] (at 1) Message not available
That indeed, would break _many_ lines of my code!
Any way to get the 'current' behaviour?
Many regards,
R�diger
________________________________________________________________
Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr!
Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
