[ https://issues.jboss.org/browse/TEIID-5624?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5624: --------------------------------------- Thinking through this a little more it seems like this will duplicate all of the engine lob tracking logic - including the need to hold statements/source results open to keep the lobs readable. This just doesn't seem like a good fit. The closest we could come would be to have the user explicitly introduce a lobid integer column to any table with a lob, then introduce a well named view, for example teiid_largeobjects that contained the lobid / lob value. The user would have to ensure that all lob ids were unique across the vdb. The teiid_largeobjects would look something like: select lobid, lob from table1 where lobid between ... unnion all select lobid, lob from table2 where lobid between ... so that we could easily filter the union branches. Then our logic for lo_open would need to reference the teiid_largeobjects table. However this is not very turn-key, so I don't think we should pursue it at this time. -- This message was sent by Atlassian Jira (v7.12.1#712002)