Data modeler: Having Maintainable Query for View Creation

Question

Hi,
I am using SQL Developer 4 and the data modeler. I typically create a view in SQL developer (from a SQL select statement). 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. This works and I can see the query for my view when I click Properties on the view in the data modeler. However, the query I see there is logically equivalent (and very similar) but it is hard to read for a programmer as carrier returns are added, the various elements of my where clause are not in the same order as I programmed them, comments (starting with '--') where not transfered with the drag and drop.
I feel I cannot only rely on the version of the view stored in the data modeler to keep my DDL code that creates the view. Maintenance of that code would be too difficult. I feel I will need to keep a separate SQL script (in a separate version control tool) containing the select statement of my view. I would then always need to make my modifications in this select statement, update my view in the database and then drag and drop the result back in the data modeler. This is cumbersome.
Do you have any solution for me? Thanks!

Answer 1

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
E-MAIL
TSSA
ORACLE
HP
IBM
MS
SAP
INTERGRAPH
CISCO
Relationship
Contracting
Performance
Architecture
Supplier Feedback
Comment
jjjjjnn Bixxxxxff
[email protected]
Yes
Yes
Yes
Yes
x
Added as requested by Sanet Mulder
itha CCCniah
[email protected]
Yes
Yes
Yes
x
x
Elliot dan
[email protected]
Yes
x
x
x
Ger que
[email protected]
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
x
x
x
isha Per
[email protected]
Yes
x
John Rato
[email protected]
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 protected]