hello Vladka and TDM team,
first I want to say thank you for all the time you spend for your community. I think a product will never be perfect, so its up to the developer to listen to new suggestions and problems their customers face. and you doing a great job on that. but lets go back to “work”, I would like to answer your comments.
b] Yes, when you make acopy of entity, you create a new entity. It has a new name, however asit’s a copy, the content is the same as in the original entity - sameattributes, same keys etc. (of the same name).
I disagree on this, for me it makes no sense to copy a table, give it a new name, but leave everything else like the original table. take the programm excel for example, if you copy a cell, its not only a different name for the cell, more importend the content can change aswell and thats a very nice feature. as we all know, you cannot have the same objectname in the same schema. so why keep the name for the keys ? I mean your own function to verify a model will find a warning if you copy a table. so if you copy an object, changing the content aswell is nothing bad, when you make the change at the right place.
d] When you select the domain in the EntityProperties form, Attributes tab, directly in the grid, also data types,user data types etc. are available. However, if you edit the attribute,see the Domains box where you can find/select only domains.
thats true, if I edit a attribute, I have a box for my domains only. but when I add attributes to a table, I dont want to open the extra edit window for every attribute. I would like to use the table window to assign the domains to my attributes. I have about 12 domains I use, but when I change the data type, I have a big select box with domains mixed with “real” data types. would be nice to have an option somwhere “only show domains as data types”. its not only a time saver, its even more easy not to use a standard data type by accident.
e] Theobject ‘Directories’ in Oracle is not linked to schema, so it is alwaysgenerated. In Toad Data Modeler, you can disable generation of thisobject - from the OTPs list, clear the Directories checkbox.
of cousre you are right again, you cannot assign a directory to a schema, but thats not what we need. your programm offers to have more then one schema/user in one model. if you generate the DDL script, you can select which schema you want to create. lets say I have 3 different users in my model, I create them one by one, so I have 3 different DDL scripts at the end. and all 3 scripts will have a DDL statement to create the directory. maybe that makes sense in some cases, but for me one statement for one model is enough. so what we need is not to assign a directory to a schema in the database, but we need to assign it to the “creation time”. when we generate the DDL script over all users, then its clear we need the statement for the directory. but when we dont generate the hole model, then the directories need a mechanism, when to create them.
f] See the Model menu | Schema/Owner Assignment.
well, I watched the movie, but this is not what I am looking for. in my opinion you need that function only, when you have more then one schema/user in your model. if not, I dont need to assign an objekt to a user, cause all objects belongs to the same user. so lets assume the case we have three users again. for every user I use one or more workspace, but I dont mix objects from different users in the same workspace. now I have to make sure, every object belongs to the proper user. I can do it when I create a new objects, but thats risky cause sometimes you just forget it. and cause I have more then one user, I cannot use the check box to assign them all to just one user. but when I have the option to assign all objects from one workspace to a user, it would safe a lot of time and less mistakes.
let me say some more words about modeling in general. for me I use a data modeler for three main reasons (of course there are more good reasons to use a modeler).
- I have a graphic overview of the model, for myself and also for other persons.
- I can safe a lot of time
- I can avoid mistakes, make the model more safe
so the functions should based on design, speed and safty. I am not a designer, so cannot say much to that point, but the mechanism you use in a modeler to safe time and make it more safe are the same you use when you programm or if you want, the same how I design my data layout. The word I am looking for is . I dont want to do the same work more then one time. that belongs to many objects in the modeler, data types, attributes, tables, workspaces and much more. the better functions you offer to control my model, less time I will spend to create it and less mistakes I will make.
ok, besides that I have one more problem. I have about 6 users in my model, thats why I assign objects to their users. now I would like to generate the DDL script, not only for one user, but for all of them. how do I fire the script at once in my database ? I mean the obejcts from different users need different connections, yet I cannot see how to handle it without making scripts for every user…