Comments
Sort by recent activity
Hi Aaron,
You are right about the dropbox links. Here are public versions https://www.dropbox.com/s/9f8pj5to7z2p9u6/0002.jpg?dl=0 https://www.dropbox.com/s/bz6wgxwm79qiw3t/0003.jpg?dl=0 https://www.dropbox.com/s/8yn7j8m5knvhw0d/0004.jpg?dl=0 https://www.dropbox.com/s/fv85zt6jgi00dog/0005.jpg?dl=0 https://www.dropbox.com/s/j4ul3vrr8yrxn4a/0006.jpg?dl=0
I'll following your instructions / comments
Hi Aaron,
You are right about the dropbox links. Here are public versionshttps://www.dropbox.com/s/9f8pj5to7z2p9u6/0002.jpg?dl=0https://www.dropbox.com/s/bz6wgxwm79qiw3t/0003.jpg?dl=0https://www.dr...
Hi Aaron,
Thanks for the update. I did the tests again.
Either I don't understand how it should work or something is wrong with my installation?
The sql objects (udf,sproc and table) reside in another database that I'm in but don't show up in the intellisense.
Also, I saw the screenshot below in the Prompt changelog. It looks different than mine right? esp. the schema that is prefixed in the changelong version. [image] / comments
Hi Aaron,
Thanks for the update. I did the tests again.
Either I don't understand how it should work or something is wrong with my installation?
The sql objects (udf,sproc and table) reside in anot...
Hi Aaron,
That would be great and I'll be more than happy to test it for you
"we just suggest the immediate children of the object used for qualifying."
When you are in a database and don't qualify with a schema Prompt will suggest all the objects no matter what schema they belong to. That is the behavior we see and is very helpful. So in this case the current Prompt thinks further than the immediate children.
Of course, once you qualify with a schema, the objects are suggested are scoped to that schema (container).
A database name is a also a container but most of the time you have a sql object in your head and since its not in your current database you forget to type the extra container, the schema.
Happy coding, Tom / comments
Hi Aaron,
That would be great and I'll be more than happy to test it for you
"we just suggest the immediate children of the object used for qualifying."
When you are in a database and don't qualify...
It's actually simple now that I had a night sleep.
Only when a schema is specified the developer wants to scope the suggestions to it. Otherwise the developer probably has just the object name in mind.
Thats how I at least think, in term of object names (and database names).
I think the majority of tsql developers don't use schema's. We just recently started using them and then the suggestions are sometimes too limited because Prompt is expecting a schema name. / comments
It's actually simple now that I had a night sleep.
Only when a schema is specified the developer wants to scope the suggestions to it. Otherwise the developer probably has just the object name in m...
What a fantastic release / comments
What a fantastic release
Hmz this is a showstoper for me. Put it on the top pls / comments
Hmz this is a showstoper for me. Put it on the top pls
Okay, I badly phrased it.
I confirm that it is suggested somewhere in the list.
Can you confirm that it is not on top? I would expect if you type in join that the foreign tables are n1 candidates and so are on top.
Thanks,
Tom / comments
Okay, I badly phrased it.
I confirm that it is suggested somewhere in the list.
Can you confirm that it is not on top? I would expect if you type in join that the foreign tables are n1 candidates a...
I found the cause of the sync problem.
Seems like if you rename a view (maybe other objects too) in SQL EM then the internal name of the object isnt updated. Hmz
You can check this if you rename a view and tell SQL EM to geneterate the sql script. This is a source for confusion I think. Is it a SQL server bug? / comments
I found the cause of the sync problem.
Seems like if you rename a view (maybe other objects too) in SQL EM then the internal name of the object isnt updated. Hmz
You can check this if you rename a ...
bump / comments
bump
fixed with build 6.3.0.235. Thanks Aaron! / comments
fixed with build 6.3.0.235. Thanks Aaron!