My current project heavily works with Oracle global temporary tables. The (main?) point of those is that data therein are visible only to the session that wrote it. They are filled in a procedure. Now, if I run that procedure for test purposes, I need to reconnect my connection manually. It would come in handy if there was a client-side command that reconnects the then used session. To me, it would be completely fine if the command was only allowed as the very first command of a file/buffer such that implementation would only need to check the "first" line for this command.
Varma hälsningar
Thiemo
1 Comment
Peer Törngren
said
about 1 month ago
Hi Thiemo,
That could potentially be a useful improvement; I'll register your request and bring it up for discussion.
Thiemo Kellner
Hej
My current project heavily works with Oracle global temporary tables. The (main?) point of those is that data therein are visible only to the session that wrote it. They are filled in a procedure. Now, if I run that procedure for test purposes, I need to reconnect my connection manually. It would come in handy if there was a client-side command that reconnects the then used session. To me, it would be completely fine if the command was only allowed as the very first command of a file/buffer such that implementation would only need to check the "first" line for this command.
Varma hälsningar
Thiemo