LOB variable no longer valid after subsequent fetch

最新推荐文章于 2018-10-30 18:45:19 发布

desert3

最新推荐文章于 2018-10-30 18:45:19 发布

阅读量617

点赞数

分类专栏： Python 文章标签： Oracle Python Access HTML .net

本文链接：https://blog.csdn.net/desert3/article/details/83772220

版权

Python 专栏收录该内容

28 篇文章 0 订阅

订阅专栏

cx_oracle读取oracle wm_concate函数操作过后的长文本clob字段，当使用fetchall或者fetchmany读取数据时，报上面的错

参考下面的文档，发现只能使用下面2种方式中的任一种来操作数据，总体来说，大数据量时读取效率不高。
通过to_char(wm_concat(brand_name))把clob字段变成varchar字段后，再采用cursorSelect.fetchmany(1000)，对于30W条数据的处理时间从10分钟减少到1分半！

for result in cursorSelect:

尝试了几次感觉效率比下面的稍微好点
或者

result = cursorSelect.fetchone() 自己控制while循环读取

参考[url=http://cx-oracle.sourceforge.net/html/lob.html]Lob objects[/url]

Internally, Oracle uses LOB locators which are allocated based on the cursor array size. Thus, it is important that the data in the LOB object be manipulated before another internal fetch takes place. The safest way to do this is to use the cursor as an iterator. In particular, do not use the fetchall() method. The exception “LOB variable no longer valid after subsequent fetch” will be raised if an attempt to access a LOB variable after a subsequent fetch is detected.