Is there a canonical way to deal with class data members that map to CLOB fields in the database? When I map to Oracle tables containing CLOB's, I get an exception from cx_Oracle about the LOB-locator object being invalidated by a subsequent fetch when I reference the CLOB member of the mapped class in code.
What I think needs to happen is that when the class member is created, instead of making it refer to the cx_Oracle LOB-locator itself the member should be set to the result of locator.read(). Is this something that'd have to be patched into the engine/driver, or can I handle it in a mapper extension? I'm using SA 0.3.1 at the moment -- might there be better CLOB support in 0.3.4? Thanks, Bryson --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
