Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Feature/two output buffers #888
Conversation
Changed how delete from output buffer table is handled - use ROWID. Increased fetch size from 100 to 3000 rows for output buffer.
Decreased read limit back to 1000 as it should not have significant performance impact anymore.
Fixed bug with increasing `max_message_id` even when nothing was read.
Now we have separate buffer for CLOB data and VARCHAR2 text data.
|
I installed the branch I will need to adapt the current implementation for the SQL Developer extension on my branch I'll change that to the way suggested in utPLSQL/utPLSQL-cli#140 - That is not a problem at all, especially since it is a development branch only. I see this PR as a quick fix for the problems introduced with the change from VC2 to CLOB. However, I think we can do better in terms of API design (making it more narrow, less redundant and more independent of the implementation) without compromising performance. This can be addressed in dedicated issues and coming releases. |
This feature will require changes on cli.
See: utPLSQL/utPLSQL-cli#140