first of all, congratulations to the new version, hope you are not that busy those days, now TDM 4.0 is alive.
I just installed the new version of TDM 4.0.6.13. And after it I opened my models from 3.6 most of it looks ok, could not find any big issue so far. Just the lower border line of a table seems to be to close to that last attribute (Recalculate Size is activated). Specially when you change the Pen Width from 1 to any other value, it will cover the last attribute. Same is with the top and the side borders, if you make the Pen Width very big. It looks like the size of the table is not growing, no matter which Pen Width you have, so the borders are “walking inside the table” the bigger the border is. I would suggest to change that behavior…
But before I find more issues, I would like to know, is there any PDF User guide for TDM 4.0 I could download ?
thanks, and belive it or not, we’re still really busy with the new version. And the versions to come.
And to the problem of Pen Width/border lines: We have already registered this issue, but as a part of autolayout and resizing. To have it dealt as a separate issue, I created change request CR 88237.
thanks for the link to the Users Guide. I have another issue and dont want to open a new thread. I will just use this one here. When I add a new View the SQL tab is not active, even I add some SQL code to it. I guess thats the same reason why the SQL Preview is not working. My old views are working fine, only have problems with new Views. I found out you need to activate the box SELECT in Views as Text. I guesss the reason is the new function, that you can build a view by clicky clicky . Is there any way I can change that behaviour, so when I add a new view, the box SELECT in Views as Text is already active ?
yes, the solution is to change value to True in Deafult Values. See the screenshot.
Apply the change and restart TDM. It should work in your model then.
I only looked in options, but thank you for that hint, thats was what I am looking for. I will keep this thread open if that is ok, in case I have more questions coming. but thanks again for the very good and quick support.
there is one big advantage of the new feature. When you create a View visually and then update some column name in linked table, Toad Data Modeler will update also the View! This feature doesn’t work on views created the old way - via manually specified SQL.
that is true, there is an advantage when I change a column name, but it also has some drawbacks. I need to create views with tables from another database (different model). also my views have a very complex code, a lot of subquiries, etc. and I never use the implicit, always the explicit sql syntax for joins. I need to be able to add hints or coments. maybe that is all possible with the new generator…
PS: One more Question, I will read the Users Guide, is there any place to report bugs and mistakes ? and is there any possibility to read it via ipad 2 ?
yes, you are right. There are some limits. I only wanted to make sure you know the advantages
You can report bugs here in this community. We usually create change requests for reported bugs. IDs of externally reported bugs then appear in Release Notes.
