Rename table
I want to rename a table and add a few columns. How can I put this into Toad Data Modeler and create the correct alter script?
Do you have an idea to improve Toad Data Modeler? We want to hear it! Idea Pond is a site where you can tell the development team what you want, and tell us how important it is by submitting, voting, and commenting on ideas. Just sign in and submit your idea in the box below.
Idea Pond is just for submitting enhancement suggestions. If you need help or found a bug, please join our forums for assistance. See our FAQ for more information about Idea Pond.
I want to rename a table and add a few columns. How can I put this into Toad Data Modeler and create the correct alter script?
In the reverse engineering wizard you can select the tables which you want to reverse engineer. You can type the name of the table in the 'select tables'-field. I think it would be usefull that you automatically go to the typed table in the Tables-grid.
With a lot of objects in single categories, it would be usefull to divide them into some groups.
For example having 100 functions, splitting it into functional groups might optimize the work. in that case possibility to create subfolder in functions subtree would be the case.
Current way of generating indexes (CREATE INDEX) requires INDEX privilege and often fails on shared hosting machines. Adding index using ALTER TABLE syntax requires only ALTER privilege which is usually available.
Please add create index method selector for MySQL while generating DDL
MichalK
In current state (TDM v4.1), all functions, even originated from different schemas, are shown as single bunch in "functions" branch.
Would be very helpful if functions will be split by schemas.
Please add Undo feature for all text fields (single line and multi-line). Missing this feature is especially annoying in sql editors.
Is it possible to make for toad data modeler a multiple-user version management? We would like to work with our team on the same datamodel and we would like to restrict it so that we won't overwrite each others changes.
Currently trying to print to A1 paper on Xerox 6204 wide format but model gets cut off. Used Bullzip print to pdf (since help recommends printing to PDF first for plotters and Bullzip supports A1). Used fit to page but it doesn't use up the whole of the printable size. Would like better support for printing directly to plotter and support for printing on A1
Provide a way to view and edit Alias files. If you want to change some attribute, you must now delete it and recreate it.
On the Table window of the Reverse Engineering and Model Update Wizards, please allow for expressions in the filter. I would like to enter something like this expression: table_name NOT LIKE ('%\_A') escape('\') AND table_name NOT LIKE ('%\_A') escape('\'). I want to eliminate tables whose names end in _A and _D
Allow comments for sequences, views and domains (if generated). Currently sequences neither have "Notes" nor "Comments. And Views only have "Notes" which are not generated into SQL comments. I know this can be worked around using the "After Script", but a "real" comment would be cleaner.
) drop the addition of "with (oids=false)" completely in the generated SQL (if it's unchecked). It only clutters the generated SQL and nowadays does not server any purpose as it's the default anyway (as oids are deprecated).
If Generate checkboxes will be set for each workspace separately it would help while generating parts of complex schemas, especially while using per schema generating. There are often situation, big model is split into workspaces in way that different workspaces contain the same objects (ie entities). Developing new part of system, we may add some existing objects into workspace and then create new ones. But while generating, ...more »
If Generate checkboxes will be set for each workspace separately it would help while generating parts of complex schemas, especially while using per schema generating.
There are often situation, big model is split into workspaces in way that different workspaces contain the same objects (ie entities). Developing new part of system, we may add some existing objects into workspace and then create new ones. But while generating, we want to generate only new ones.
We can use Generate checkbox for that. But while working on few new subsystems, it cause constant need of rechecking objects for generation.
In such cases would be really useful if Generate checkbox will be stored on per workspace basis.
Maybe there would be need to add just another checkbox for this feature. Or maybe this additional checkbox should be names "skip Generate for current schema"
« less full details »
What about generate reports based on some templates?
So any one will be possible to create own template or modify default one, without knowledge of programming. Current state (TDM v4) is not perfect solution for documentation: reordeing items, hiding elements is impossible without programming custom reporting class
What about making possible an indention of selected text by hitting Tab or Shift+tab.
To enhance documentation abilities of TDM, I suggest to add possibility of formatting text while writing notes. Bold, italic, underline, fixed width font for code citation, colours, ordered and unordered lists would be useful.
Most of those features are available in rtf editors and may be easly converted into HTML while generating reports.
I would like to add description to each single argument of the functions for further generating into reports.
To achieve that, each argument should be added as separate object. In the same way as columns for tables (pgAdmin does it this way).
Selecting datatypes from droplist would also help avoiding typos.
Current Return Data Type field is quite small in case of entering return Table declaration. Bigger field would be fine. however I have idea to replace it by drop list containing available datatypes. When Table selected, a form for entering single fields and datatypes should appear
There's no null/not null attribute in domains..
maybe could be interesting to have it? so you can have domains like: "MANDATORY DESCRIPTION".. "OPTIONAL DESCRIPTION"...
Currently I'm noticed lack of workspace name in Stamp element. I can feel that there might be another data like total number of pages of workspace.
Would be nice to have possibility of adding graphical representation of schema onto workspace.
Currently it may be achieved by using rectangle and some text object. But having it native would improve modelling experience.
Please add schema support for mysql. I mean, mysql works with database like with schema. it is possible to reference objects from another schema than current one set by USE command. Also relation constraints are possible between databases (schemas). In other work, what is historically named as "database", work as schema. Even in native MySQL software, name has been changed into "schema". Current version of TDM don't ...more »
Please add schema support for mysql. I mean, mysql works with database like with schema. it is possible to reference objects from another schema than current one set by USE command. Also relation constraints are possible between databases (schemas).
In other work, what is historically named as "database", work as schema. Even in native MySQL software, name has been changed into "schema".
Current version of TDM don't allow to design multi-schema mysql-based systems
« less full details »
Multiple WorkSpaces can currently be selected in the "Physical Model Explorer" (V4.1.5.8). It would be handy to be able to print the selected WorkSpaces in one shot. Currently each WorkSpace must be printed one by one.
Idea is described also on forum, including screenshot of example: http://modeling.inside.quest.com/thread.jspa?threadID=36969 Point is to allow selecting some default datatypes just from ADD button drop down menu (see attached picture) without need of using on-grid comboboxes which are just slow. Values shown in drop box should be editable in global config, or projectconfig (in best case both, when project would derive ...more »
Idea is described also on forum, including screenshot of example: http://modeling.inside.quest.com/thread.jspa?threadID=36969
Point is to allow selecting some default datatypes just from ADD button drop down menu (see attached picture) without need of using on-grid comboboxes which are just slow.
Values shown in drop box should be editable in global config, or projectconfig (in best case both, when project would derive from global settings allowing some changes), Theoretically number of entries may be unlimited, but from my experience 3 up to 5 is enough.
Defaults should contain data type and its size (if needed). It may also define Not Null constraint (which might be shown by NN tag next to name).
I will put it into Idea Pond, but IP doesn't allow to add attachment, so I made use of forum to achieve this
« less full details »
Social Web