Comments
Sort by recent activity
Oh yes. This would be great! / comments
Oh yes. This would be great!
Hi David,
oh, I did not know this button. It's really useful. Thanks for the hint. It does exactly what I was looking for (however not for triggers). / comments
Hi David,
oh, I did not know this button. It's really useful. Thanks for the hint. It does exactly what I was looking for (however not for triggers).
Hi David,
thank you for fixing this issue. I confirm that the generated script now also contains the owner name of the table, even if the trigger owner was manually typed.
Including the table name in the suggestion list is very useful, too. Would it be possible to show the owner/schema of the table, too?
Currently in suggestion list:
Trigger_Name Table_Name
Suggested suggesion:
Trigger_Name Schema.Table_Name
/ comments
Hi David,
thank you for fixing this issue. I confirm that the generated script now also contains the owner name of the table, even if the trigger owner was manually typed.
Including the table name ...
Hi David,
displaying the owner name seems to be a little inconsistent for now: Schema/Owner is displayed for tables, but not for views, procedures, functions, triggers and synonyms.
We would find it useful to have the schema always in the suggestion box. / comments
Hi David,
displaying the owner name seems to be a little inconsistent for now: Schema/Owner is displayed for tables, but not for views, procedures, functions, triggers and synonyms.
We would find i...
Hi David,
no, the error occurs when after typing the owner name of the trigger, then choosing the trigger from the suggestion list. After that SQL Prompt auto-completes the ON clause and the table name (forgetting the owner of the table). / comments
Hi David,
no, the error occurs when after typing the owner name of the trigger, then choosing the trigger from the suggestion list. After that SQL Prompt auto-completes the ON clause and the table ...
I realized that current version is 2.0.1.53 superseding 2.0.1.36. Do you have any change logs for us? Release notes do not reflect them on http://documentation.red-gate.com/displ ... ease+notes / comments
I realized that current version is 2.0.1.53 superseding 2.0.1.36. Do you have any change logs for us? Release notes do not reflect them on http://documentation.red-gate.com/displ ... ease+notes
Hello,
I was surprised to find SQL Search version 2.2 on your download site. What are the changes after 2.1? Release notes do not show them: https://documentation.red-gate.com/disp ... r+versions / comments
Hello,
I was surprised to find SQL Search version 2.2 on your download site. What are the changes after 2.1? Release notes do not show them: https://documentation.red-gate.com/disp ... r+versions
OK, 6.3.0.70 fixes that one. Thank you! / comments
OK, 6.3.0.70 fixes that one. Thank you!
Thanks Aaron! / comments
Thanks Aaron!
Aaron,
thanks for the new version. It's partially working: It seems that we have a semicolon issue here again.
If the ii snippet is defined as
INSERT INTO $CURSOR$ WITH (TABLOCK)
it gets correctly expanded to
INSERT INTO TableName WITH (TABLOCK)
(ColumnName)
VALUES (0 -- ColumnName- smallint
)
However, if the snippet is defined as
INSERT INTO $CURSOR$ WITH (TABLOCK);
(note the trailing semicolon) and I start typing ii+TAB: this leads to
INSERT INTO | WITH (TABLOCK);
(The pipe indicates the cursor position) So everything is fine until now. But after choosing a table name, the generated code gets replaced by:
INSERT INTO TableName
(ColumnName)
VALUES (0 -- ColumnName- smallint
)
...the table hint and the trailing semicolon are missing after full generation of the code. / comments
Aaron,
thanks for the new version. It's partially working: It seems that we have a semicolon issue here again.
If the ii snippet is defined as
INSERT INTO $CURSOR$ WITH (TABLOCK)
it gets c...