Idea Pond is where you can tell the development team what you want and how important it is by submitting, voting, and commenting on ideas. Just sign in and click the "Submit New Idea" button to submit your idea.

So, you have an idea to improve or add a feature?  Great.  We want to hear it!

See an existing idea in the Pond that you like?  Vote it up!  Don't let it sink to the bottom and become pond scum. 

Is there an idea that you totally disagree with?  Start by voting it down and then leave your comments why.  Remember, this is your product too!

Idea Pond is just for submitting enhancement suggestions. If you need help or found a bug, please contact Quest's Product Support. See our FAQ for more information about Idea Pond.

All Ideas

me_the_first
Follow / 12 Jul 2017 at 10:50am / General features

Firebird support

Firebird is open source relational database. Was supported in Case Studio (TDM before renaming) and TDM until version 3.0. Many companies are using Firebird and thats giving them 3 options: 1: stay on Firebird and change modeling tool 2: stay on TDM and...
0 / Active
Rod
Follow / 19 Jun 2017 at 10:45pm / Others

Does TDM support AWS?

I would like to know if Toad Data Modeler support Amazon Web Services? or if there is any plan for it, thank you,
1 / Active
costabas
Follow / 24 May 2017 at 5:48pm / Modeling

Add the ability to provide "verbs" on both ends of a relationship

As an example, from the video rental model, a Customer borrows movies, I wanted to add one caption on the Customer side, "Borrows", and on the other side, "Borrowed by". I used before ER/Studio from Embarcadero and you could add...
0 / Active
maurycy.widera_765
Follow / 18 May 2017 at 9:34am / General features

Generate SQL script for both Oracle and MSSQL

Hi, Our solution is database agnostic - it can work on both Oracle and MS SQL server. Currently it is not possible to generate both Oracle SQL and MSSQL scripts out of a single TDM model. Thanks, Mau.
0 / Active
Daril
Follow / 17 Mar 2017 at 6:28am / Modeling

Keep Attribute migrated by Relationship

When user create relationship from parent entity to child, attributes from parent entity are migrated to child. When this relation is deleted, attributes are deleted too. It would be nice have some possibility to change this behavior. For example chechbox...
0 / Active