LOB fetch behavior

vladzak

Member²
If I understood correctly, current behavior of PL/SQL Developer when fetching rows with LOB columns in either SQL Window or Test Window is to fetch LOB contents along with the row. Can this be changed (and made configurable with a preference) to deferred LOB fetch (that is, until I click the ellipsis button to inspect LOB contents,) because if LOBs are large enough, fetch takes really long time, especially over relatively slow channels, and fetched data consumes a lot of local memory even though LOB data may not really be needed.
 
I love using PLD. It works great for local databases and is rich featured and simple to use once configured. But I keep getting complaints from users in my company about it being slow or "unusable" against our production databases.

Our main tables contain lobs and there is a high latency between our development and production environments. As most users just "select *" from the main table with some kind of a where clause (ususlly using "query by example" or double clicking a table in the Objects Window), the result is waiting a long time (0.1 sec latency * 500 rows = 50 sec) for a simple query the database peforms without effort. Same query on a table without lobs returns in 1 sec, which is tolerable.

Is there any kind of solution to ease the pain (make PLD fetch a lob column only when clicked or use substr around lob columns as you do with to_char and date columns etc.)?
Do you have plans to address this issue?
 
I vote for this enhancement, too. Plus, this should also be done for XMLTYPEs, but that's a lot trickier. Their current handling is pretty bad, anyway. One solution could be query rewriting with xmltype.getclobval().
 
Back
Top