Might I suggest you're doing it 'backwards?'
You might get closer to what you're looking for if you were to build the view in the modeler first. Version control it there, and then push it to our database(s) as needed.
You an ask the modeler to 'Use SQL Developer Formatter' in the preferences which will use the SQL Developer formatter preferences when generating the DDL.
Can you give an example of the commented code not coming over correctly? Are you saying you see these in the SQL panel of the view in SQL Developer, but they're not preserved in the model when importing them? -- Comments generally aren't stored in the data dictionary.
I then drag and drop the view to the data modeler in order to have it stored for the next time I regererate the database schema from the data modeler.
If you don't want to use Query builder then there is a solution for you:
1)Don't use QB for just seeing select statement - use "DDL Preview " on that view.
QB always parse and reconstruct the query (and loosing comments - we have a bug logged for that) so you won't see original select statement
2) Don't use "Parse older style views"functionality - I logged a bug against that functionality because it changes view definition without need
3) Make sure "Use SQL Developer formatter" is not set in "Preferences>Data Modeler>DDL" - otherwise definition will be formatted according formatting rules set in preferences
Hi Jeff would you be able to help me in creating a data model cause im really stuck with this one .Basically if been asked to create a survey application in oracle apex that use to excel based . So the info i was given was in a form of excel sheet which looks like this
USER'S VENDORS TOPICS
NAME TSSA ORACLE HP IBM MS SAP INTERGRAPH CISCO Relationship Contracting Performance Architecture Supplier Feedback Comment jjjjjnn Bixxxxxff Bis@esko.co.za Yes Yes Yes Yes x Added as requested by Sanet Mulder itha CCCniah niJ@ymail.co.za Yes Yes Yes x x Elliot dan A@eskm.com Yes x x x Ger que email@example.com Yes Yes Yes Yes Yes Yes Yes Yes x x x isha Per Key@em.co.za Yes x John Rato Rat.firstname.lastname@example.org Yes x x
So where it says yes thous are the vendors that people associated with them have to asses and where there's an X thous are the topics that the vendors have to be rated on . So if for example the first guy on the list jjjjjnn Bixxxxxff will asses TSSA , ORACLE , HP , IBM , MS , SAP on the topic of Architecture and if you look at the second user itha CCCniah he would rate TSSA , ORACLE , INTERGRAPH on the topics of Relationship and performance . Any idea how i could data model this to get my table structures right .so that features like completion status could be displayed to the user through APEX which can only be done by a correct data-model i have tried normalization but i did go anywhere becauce there are so many variations any idea on how you would go about data modeling this would be greatly appreciated thank you If you would like a better copy of the table my email is email@example.com
A few things:
- please don't hijack threads, start new ones if you have a new question
- your data is live for everyone to see, including your colleagues and their email addresses
- I'm not really available for data modeling consulting, but if you have specific tooling questions, we're happy to oblige
Hay Jeff thanks man i changed the email address before posting that question so the data isnt real any one you may have in mind that could help .