Re: [MonetDB-users] Large transactions or large updates
On 21 Nov 2006, at 2:57 PM, Ronald Oussoren wrote:
I'll see if I can create a script that demonstrates the problem,
I found the problem, my data was not as clean as I expected and I tried to insert a non-ascii value into a string column in the database.
That still leaves the lame error reporting (raising RuntimeError (None)) in the MonetSQLdb wrappers. The MapiClient does report a useful error and I've tried to compare this with the Python bindings. It turns out that the error-checking code in the python binding has ample room for improvement. I debugged my code by adding calls to mapi_error, mapi_result and mapi_explain_query to the C code of the mapi_query wrapper, but that's obviously not the right solution.
Ronald
On 2006-11-23 12:17, Ronald Oussoren wrote:
On 21 Nov 2006, at 2:57 PM, Ronald Oussoren wrote:
I'll see if I can create a script that demonstrates the problem,
I found the problem, my data was not as clean as I expected and I tried to insert a non-ascii value into a string column in the database.
That still leaves the lame error reporting (raising RuntimeError(None)) in the MonetSQLdb wrappers. The MapiClient does report a useful error and I've tried to compare this with the Python bindings. It turns out that the error-checking code in the python binding has ample room for improvement. I debugged my code by adding calls to mapi_error, mapi_result and mapi_explain_query to the C code of the mapi_query wrapper, but that's obviously not the right solution.
Can you make a bugreport out of this? Thanks.
participants (2)
-
Ronald Oussoren -
Sjoerd Mullender