Comments
6 comments
-
I have a list of "primary use" aliases so SP's, UDF's, etc. use the same aliases, which makes them faster to read and understand and makes them easier to maintain - for the 100+ tables in our small DB it doesn't take long to memorize them, especially if, like v3's auto-assign, you use the capitals.
How difficult would it be to plug in a simple options-pane maintaind XML doc - similar to how snippets were an XML doc in v1.4?
Naturally the alias is "suggested" not forced... In cases where a table's joined against itself, you'd obviously have to change the alias... -
I like the 'Auto' alias feature, but I think a custom auto feature like PDinCA suggested.
-
Even better: the system could learn and use the aliases already in use in the database!
-
Thanks for the feeback. I have added an option to ignore system objects to our sugested feature list.
In the final version when you type in and alias or a table name followed by a dot we will definatly only show the columns in that table/view but there seems to be some bugs atm that seem to be stopping that working.
We are recieving a lot of feedback about aliases. It seems that being able to specify some custom aliases would be a great feature. I have added it to our list of sugested features.
Lionel -
Just in case you add an option for filtering out system objects, what about a keyboard shortcut that would display only system objects and another one for SCHEMA_INFORMATION only?
-
Regarding the presence of system objects in the list, I initially thought the same thing. But in real life, it seems that they don't actually interfere with "real" objects. So far, I've always had it come up zeroing in on the directly applicable stuff, with the system objects a long way off in the list.
Regarding aliases, I rather like the automatically-generated abbreviations. Of course, that's probably because I tend to create my own aliases in exactly that way
Add comment
Please sign in to leave a comment.
It would also be a pleasant thing is the system were able to filter the candidate list from any alias used (either predefined or not). For example, if I chose Org as the alias for Organismes, then writing « SELECT Org. » should show only the fields of the table Organismes.
Finally, there should be an option for not displaying system objects.