Comments
Sort by recent activity
Ah, sorry, I guess this is the same problem report by Mike O'Neill on June 3 (under the title of "Table variables" - that's why I didn't see it at first).
Marc / comments
Ah, sorry, I guess this is the same problem report by Mike O'Neill on June 3 (under the title of "Table variables" - that's why I didn't see it at first).
Marc
David Lovemore wrote:
2007 Format
Why is it that you need to convert your docs for 2007. Do they not load automatically?
Sure, they do - but the .docx format for Word 2007 is also much smaller than the "binary" DOC format - case in point, my 46 MB *.doc is only about 11 MB in *.docx - would be neat to have the Word2007 Output option in SQL Doc 2.1 ! :-) / comments
David Lovemore wrote:
2007 Format
Why is it that you need to convert your docs for 2007. Do they not load automatically?
Sure, they do - but the .docx format for Word 2007 is also much small...
Hi Brian,
I understand what SQL Prompt is doing, and I would like it to UPPERCASE my keywords - but it should be smarter about the CONTEXT they're in when deciding whether to update or not.
E.g. if I'm typing a keyword after a "." following a XML data field, e.g. after
"EntryData." - then it should *NOT* under any circumstances UPPERCASE my "modify" - it's a XML DML keyword which HAS to be lowercase.
Also, if I'm insde a string delimited by quotes ' ..... ', SQL Prompt should NEVER EVER attempt to UPPERCASE stuff on me..... it's my string - leave me alone!
But I don't want to have to be forced to turn off uppercasing overall - I like that. Just make SQL Prompt smarter about the CONTEXT of a keyword before attempting to uppercase it........
Cheers,
Marc / comments
Hi Brian,
I understand what SQL Prompt is doing, and I would like it to UPPERCASE my keywords - but it should be smarter about the CONTEXT they're in when deciding whether to update or not.
E.g. if...
Hi guys,
looking forward to an RC and the release - I sure hope those annoyances have been ironed out. As I said - I totally love the basic idea of SQL Prompt, but the current version is just more of a hindrance than a help to me in my daily dev life. / comments
Hi guys,
looking forward to an RC and the release - I sure hope those annoyances have been ironed out. As I said - I totally love the basic idea of SQL Prompt, but the current version is just more ...
Hmm... self-joins. Interesting
You *do* like a good challenge, don't you? :lol:
Marc / comments
Hmm... self-joins. Interesting
You *do* like a good challenge, don't you? :lol:
Marc
nanchen wrote:
While it would be nice to specify alias on a per table/view basis, this is not yet sufficient: suppose that I want to join a table with itself. Then I would expect the tool to provide me with two different alias names (like myalias and myalias2, for instance...)
Good point, yes. That would be required "smarts" for SQL Prompt 3, too! :-)
Marc / comments
nanchen wrote:
While it would be nice to specify alias on a per table/view basis, this is not yet sufficient: suppose that I want to join a table with itself. Then I would expect the tool to pro...
Bart Read wrote:
So for example you could set it up in the options dialog to ignore prefixes such as "T_", "V_" etc.
Would this do the trick?
Yes, that would definitely be an option - specify some prefixes to ignore, or a number of chars to ignore.
Even better would be a way to specify manually, on a table-by-table (and view-by-view) basis, what prefixes to use. Fill those in with your best guess, but allow me to change them where appropriate and needed.
Thanks!
Marc / comments
Bart Read wrote:
So for example you could set it up in the options dialog to ignore prefixes such as "T_", "V_" etc.
Would this do the trick?
Yes, that would definitely be an option - specify s...
Bart Read wrote:
Please see my post in reply to your topic about owner/schema names: the same thing applies. We just didn't have time to fix this for the beta.
Thanks - yes, I noticed a "known issue" in the release notes, too, later on. Hope it'll be fixed in Beta 2! :-)
Marc / comments
Bart Read wrote:
Please see my post in reply to your topic about owner/schema names: the same thing applies. We just didn't have time to fix this for the beta.
Thanks - yes, I noticed a "known ...
I was a bit saddened to hear about the "final preview version" of SQL Prompt 5 being out, and this issue is **STILL** **NOT** **FIXED** ....... / comments
I was a bit saddened to hear about the "final preview version" of SQL Prompt 5 being out, and this issue is **STILL** **NOT** **FIXED** .......
The problem has been solved in a very competent manner by Red Gate support. There must have been some "gremlin" in my computer that interfered with the update process.
After uninstall and reinstall and re-update, everything works fine - thanks to Red Gate's excellent support! / comments
The problem has been solved in a very competent manner by Red Gate support. There must have been some "gremlin" in my computer that interfered with the update process.
After uninstall and reinstall...