Comments
Sort by recent activity
Thanks for this. There's always something that slips through. As you've no doubt guessed, the first item is of much greater concern to us than the second. The frustrating thing is that I fixed it this afternoon in less than 10 minutes, however because we've just switched to a new branch, it's not been integrated into our build system it's just sitting on my office desktop at the moment.
Our plan is to see if anything else comes up over the next week, fix any major problems, of which we hope there won't be many, and then get a patch out within the next 4 weeks or so. This first problem is really very irritating, but things do occasionally slip through despite our best efforts. Sorry for any inconvenience.
Thanks,
Bart / comments
Thanks for this. There's always something that slips through. As you've no doubt guessed, the first item is of much greater concern to us than the second. The frustrating thing is that I fixed it t...
Nice, that is very handy indeed. / comments
Nice, that is very handy indeed.
Another really useful snippet there. Thanks. / comments
Another really useful snippet there. Thanks.
Interesting. I would have thought that would work and I'm not really sure why it doesn't. We'll look into it.
Thanks,
Bart / comments
Interesting. I would have thought that would work and I'm not really sure why it doesn't. We'll look into it.
Thanks,
Bart
Sorry, no I was being lazy and didn't read your post properly. The popup behaviour can be configured on the "Pop-up Behaviour" tab in the options dialog. Click SQL Prompt > Options on the main menu of your editor.
Generally SQL Prompt only pops up the list once you've started typing a word, so you need to enter at least one character, however if you go to the "Triggering" screen you'll see a list of words after which the popup is automatically triggered. This explains the difference in behaviour you're seeing since by default Prompt is configured to pop up after WHERE.
Hope that helps.
Thanks,
Bart / comments
Sorry, no I was being lazy and didn't read your post properly. The popup behaviour can be configured on the "Pop-up Behaviour" tab in the options dialog. Click SQL Prompt > Options on the main menu...
I tried that too just to be sure what would happen (it's so long since I wrote the popup trigger code) but as you say, it didn't do anything. It's something we might consider for the future. I can certainly see that in the SELECT column list, or in the GRANT/REVOKE/DENY column lists, as well as a few other places that behaviour would definitely make sense.
Thanks,
Bart / comments
I tried that too just to be sure what would happen (it's so long since I wrote the popup trigger code) but as you say, it didn't do anything. It's something we might consider for the future. I can ...
Please see my other post.
Thanks,
Bart / comments
Please see my other post.
Thanks,
Bart
Well, that and it's a bit cheeky to go adding features at this stage... but all the building blocks I needed were already there, it was just a case of sticking them together properly. Our testers are going to kill me though. / comments
Well, that and it's a bit cheeky to go adding features at this stage... but all the building blocks I needed were already there, it was just a case of sticking them together properly. Our testers a...
Well, "evil" it may be, but I've just added support for it. You should find it working as you'd like in the final 3.6 release.
Thanks,
Bart / comments
Well, "evil" it may be, but I've just added support for it. You should find it working as you'd like in the final 3.6 release.
Thanks,
Bart
Sorry, I should make it clear that this only works for CREATE TABLE not SELECT INTO. I was fairly sternly warned not to support SELECT INTO because it's "evil" due to locking issues in msdb (?)... that and the fact that we didn't have time. Apologies.
Bart / comments
Sorry, I should make it clear that this only works for CREATE TABLE not SELECT INTO. I was fairly sternly warned not to support SELECT INTO because it's "evil" due to locking issues in msdb (?)... ...