×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
This is a solvable problem, I could access the column type info from
somewhere else,
There's plenty in SYSCOLUMNS. Surely you can get what you need from
there. Actually, the docs seem to nudge people toward SYSCOLUMNS2
instead, since it both has a few more pieces of information *and*
supposedly performs better, at least in some situations. But
definitely, either of those should be fine.
but at the moment it's not a critical issue for me and so
I'd rather wait and see if the fix can be done in ibm_db_dbi.
If by "wait" you mean wait for IBM to fix it... I think you'll be
waiting for quite a while. If you mean you want to see for yourself if
the fix can be done in the Python code for ibm_db_dbi, that sounds
like a worthwhile endeavor. It might be that the only remedy is to fix
the C code in ibm_db, though. Maybe Kevin Adler can offer more
insight.
Note that the IBM i version is its own thing maintained by Kevin, not
part of the main ibm_db project (despite verbiage on the main project
that implies all flavors of Db2 are supported):
https://github.com/kadler/python-ibmdb/tree/ibmi
John Y.
As an Amazon Associate we earn from qualifying purchases.