|
From: Jeffrey Z. <Jef...@q-...> - 2009-08-27 11:23:54
|
I have a problem where a Sybase.DatabaseError exception is thrown by the
python-sybase module when I execute a Sybase ASE 15.0.3 stored procedure
that contains a local variable with a name longer than 30-characters.
Here is exact error text:
Traceback (most recent call last):
File
"/home/jeffreyz/workspace-3.5/generate-client-test-data/src/generate_dat
a_run.py", line 11, in <module>
'--logging-stderr-on', '--logging-stderr-level', str(logging.DEBUG),
File
"/home/jeffreyz/workspace-3.5/generate-client-test-data/src/generate_dat
a.py", line 415, in main
generate_client(cursor, options)
File
"/home/jeffreyz/workspace-3.5/generate-client-test-data/src/generate_dat
a.py", line 271, in generate_client
'@op_AccountNumber': Sybase.OUTPUT(1)})
File "build/bdist.linux-i686/egg/Sybase.py", line 418, in callproc
File "build/bdist.linux-i686/egg/Sybase.py", line 695, in _start
File "build/bdist.linux-i686/egg/Sybase.py", line 709, in _mainloop
File "build/bdist.linux-i686/egg/Sybase.py", line 753, in _raise_error
Sybase.DatabaseError: Msg 103, Level 15, State 205, Line 13
The identifier that starts with '@tmp_HasFixedInitialCreditLimi' is too
long. Maximum length is 30.
Msg 103, Level 15, State 205, Line 14
The identifier that starts with '@tmp_HasFixedClearingCreditLim' is too
long. Maximum length is 30.
Msg 137, Level 15, State 1, Line 14
Must declare variable '@tmp_HasFixedClearingCreditLimi'.
Notice that it is complaining that the name of the local variable
'@tmp_HasFixedClearingCreditLimit' is too long.
This was a known problem with ASE 12.x. However, I compiled the
python-sybase module on Ubuntu 9.04 against:
Linux Express Edition for ASE 15.0.3
I have never installed a version of ASE 12.x, so I could not have
accidentally compiled against old libraries. The server on which the
stack trace above was created was running ASE 15.0.3 on Fedora Linux.
Does anyone know why I triggered an exception for identifiers over
30-characters when all libraries involved seem to be for Sybase ASE
15.x?
Is there a way to fix this problem so that no exception is thrown?
Regards,
Jeffrey
|