PSD is finally catching on here at my shop. The tech lead got so fed up with how SQL Navigator handles OUT or function RETURN ref cursors, he bought his own copy of PSD. Now the wonderful PSD infection is spreading. Every day he comes to me with yet another sweet feature or productivity gain he's discovered. It's fun to watch...
However, today, he approached me with something he actually misses from SQL Navigator: the ability to save an INSERT script to clipboard based on a selected set of rows from a result set grid control. I realize PSD has Export to SQL Inserts, but that's for a single table. He'd like to create an insert script from any selected result set or subset, especially the grid used to display ref cursors.
So on his behalf, I'd like to request that from any result set grid, one can select all rows, certain rows, or certain columns, right-click, and select "Copy as Insert Script...". For ref cursors, I imagine the name of the INSERT table could be derived from the OUT variable name or the type name. It can always be changed using Find/Replace or macros after pasting. For SQL queries that aren't single-table queries, I imagine the user could be prompted for the INSERT table name.
Thanks for considering this!
bc
However, today, he approached me with something he actually misses from SQL Navigator: the ability to save an INSERT script to clipboard based on a selected set of rows from a result set grid control. I realize PSD has Export to SQL Inserts, but that's for a single table. He'd like to create an insert script from any selected result set or subset, especially the grid used to display ref cursors.
So on his behalf, I'd like to request that from any result set grid, one can select all rows, certain rows, or certain columns, right-click, and select "Copy as Insert Script...". For ref cursors, I imagine the name of the INSERT table could be derived from the OUT variable name or the type name. It can always be changed using Find/Replace or macros after pasting. For SQL queries that aren't single-table queries, I imagine the user could be prompted for the INSERT table name.
Thanks for considering this!
bc
