I think there is a difference. when I understand the function of your checkbox, you place the schema name in front of the objectname, that is created, but not everywhere in the hole code of the object. lets take a procedure for example. when I enable or disbable the checkbox “Generate User/Schema to Objects”, the only thing that will change is the object name of the procedure I am creating. there are a lot of other objects inside the procedures, but none of them has a schema name before their object name, no matter if I disable or enable the checkbox. the same is, when I use an object inside the procedure and place a schema name in front of it, no change of the code.
now when I do the same for a synonym, both is changed, so not only the title but also the content of that object. even more confusing, when I refer to an object in a synonym not in the same schema both is ommited when I disable the checkbox. to use the syntax without a schema name has one advantage, I can use it for different users. but if the script is generated like it is now, I cannot use this advantage anymore, cause when I refere to objects to another schema then the one I am creating, the schema name is lost.
Thank you for your comment. Let us try to explain this issue.
The checkbox “Generate User/Schema to Objects” relates to all model except for such parts of the model where TDM doesn’t know linkage among individual objects. A perfect example of such exception is the SQL tab of procedures or views. The SQL tab is just a text for TDM and TDM cannot understand the text. TDM doesn’t identify individual objects there and therefore is not able to remove User/Schema.
The combo-box Object in the Synonym Properties dialog is a different case. It ‘carries’ the linkage to individual objects (it is not just a text), therefore the checkbox “Generate User/Schema to Objects” influences it.
We hope we managed to explain it in a clear way. If there is anything you don’t understand, please write us back. Thanks.
I understand what you want to say, for TDM it is a difference. But thats more a technical point of view. Lets asume we would have all object names as linked objects, also inside of a procedure. even then you should not remove all schema name, specially not when the schema name of the created item is different from the schema name used inside the procedure. The advantage to remove the schema names in front of my objects is, I can create the object under different users. but if you remove all schema names, thats a disadvantage, cause the schema name can refer to an object of a different user, not the one I am creating the object. and thats excactly what happpend in my model, I referred to a different schema in my synonym and with the checkbox disabled, the programm removed both. so you should only remove it, when the schema name of the created object is the same.
…
If you want to generate it another way than it is now, you can do the following:
Open the Synonym Properties dialog, from the Object box select and click the After Script tab where you can write a command, e.g.:
CREATE PUBLIC SYNONYM SynonymName FOR SCOTT.TableName
/
would be nice if you could copy an existing workspace with its objects shortcuts into another new one.
when you add objects to a new workspace, I can only add tables and relationships to it, but not notes or other objects. maybe that feature exists already and I cannot find it.
when I add both tables to a workspace, would be nice if I get the relationship aswell.
not really a feature, but would be nice aswell if the TDM webseite would have its own favicon
Yes, it would be very nice.
This request has already been raised. - Clone/Copy WS - CR # 46 002. Unfortunately, this CR hasn’t been included in our feature coverage plan for next TDM release 3.5, however we plan to work on it for some of other future versions. Thanks for your patience.
If you mean that you want to add shortcuts of these objects on various Workspaces, you can create shortcuts of the following objects: Entity, Relationship, Inheritance, View, Materialized View, Note, Stamp, Category (caption of Category)
Drag&drop e.g. the Note from Model Explorer to the WS, or use CTRL+SHIFT+drag&drop on the Workspace.
Thanks for your suggestion.
If you have any questions, other recommendations etc., please write us. Thanks for your great co-operation!
I mean a different way to add Objects to the workspace. When you right click on a workspace, you can “Add Selected Objetcs to Workspace”. In the new window you can add tables and relationships to the workspace, but not other objects like notes.
I see, in the Add Selected Objects to Workspace dialog there are buttons Shapes and Links. Under Shapes, shortcuts of entities and views* are displayed. You want also Notes.
I’ve created a new CR for it - 67 415.
Thanks!
Note: We reduced the list only to entities and views as in big models the list can be very long.
actually I would like to have the possibility to add all objects in that window/list a workspace can contain. Of course that list will get bigger, but when you add more filters all is fine.
just a very small issue, when I generate a script, I get a “Grant permissions section” even I have not Grants…
also it would be nice to format the text in notes a ittle bit, nothing big just bold, center, etc. And when you recalculate a note that new size looks a bit strange to me.
just a very small issue, when I generate a script, I get a "Grant permissions section" even I have not Grants....
Yes, it behaves this way. We do not plan to change it for now.
it would be nice to format the text in notes a ittle bit, nothing big just bold, center, etc.
Thanks. I've created a new CR for this. 67 518
when you recalculate a note that new size looks a bit strange to me.
What exactly do you mean? Could you please send us a screenshot?
When does the problem occur? Do you have Recalculate Size option selected by default? What change do you make?
this is the note after the recalculation of the size. its seams too big for me, there is only one Word inside of the note. On the other hand a temp table should have a different outlook as a normal table or at least a different color by default.
Yes, we define minimal size for the Note shape. We can make it smaller. CR # 67 537.
Formatting of Notes: At the moment you can only select the Notes on the Workspace (SHIFT) and format this selection. Unfortunately, it is not possible to define different format settings for notes, entities etc. in Options. However, we will see what we can do about it. I’ve added your comment to the CR # 67 518.
another very, very small issue. When you use the feature schema/user assingment, you can check only for objects without an assingment. I do this to check if I forgot a table to assign to a user/schema. so its possible you dont have anything to check. A small message would be helpful, that there is nothing to check, rather then hit the button and nothing happens.
Found something else. When you export or import the dictionary, you cannot choose what you want to import or export. For example I use the dictionary for different models (guess thats the import export function for), cause I want to use the same domains for all my models. Now when I have do add a new domain/type, etc. I have to update one model. Since you dont have repository for all models, I need to export it and then use the import function for all the other models. well, now I got the same domain twice, since I had to export the old ones aswell. would be nice if you could single select them or use a check box to import only new ones.
an another problemen. When you saved your model and after it change the order of generated objects, you cannot safe again. it looks like that this change does not count for saving the model again. then when you close the model, the change of the order get lost.
Schema/User Assignment - I’ve created a new CR # 67 789.
Workaround: Select also the Confirm before Assignment checkbox. When you are not asked to confirm, there isn’t any object where the schema shall be assigned.
Import/Export Dictionary - Yes, all dictionary items are imported/exported, so you can get the same domain twice. We will see what we can do about it. Thanks! CR # 67 792.
