Forum for SQL Developer and Data Modeler?

I searched now for a while all the available forums but did not found a special forum for the Oracle SQL Developer tool.
Where do I post questions about it?
Is there another, separate forum for SQL Developer Data Modeler?
Peter

https://forums.oracle.com/forums/category.jspa?categoryID=501

Similar Messages

Links for SQL Developer and Data Modeler not working?

Hi folks,
I tried to access the new SQL Developer and Data Modeler links posted in the April 1 message (and on the Oracle site) from a couple of machines with no luck (empty zip files) - is there an update to the links?
Thanks!
Tomo

In Firefox zero length zip. In IE loses connection to downloads.oracle.com.

Integration of SQL Developer and Data Modelling - concerns.

In aanother thread about OSDM connections, I commented that the development team for OSDM and the core product seem to separate and Sue responded.
Sue Harper wrote:
A clarification of the Data Modeling feedback application and this forum. The developers are part of the SQL Developer development team, but as for all our features, each developer has a focus area, so the Data Modeling developers will tend to answer those questions. The reason I said that they seem to be separate as that ODSM seems to be put together completely differently. I hit another example today. I downloaded a fresh copy of osdm without JDK. On starting it up, it complained it couldn't find a jre and quit. There was no prompt to specify the location as there is with SQLDevloper and there are no configuration files to edit.
SQLDeveloper already has issues with different components doing the same differently. The number of problems has been reduced but it has taken some time and I am concerned that the introduction of a large body of new code will cause things to revert to the bad old days in terms of quality.
I may or may not end up using OSDM, but I want to have the choice. I don't want components I don't use becoming part of the application and adding bloat. The migration components are a case in point. The "migration workbench" ought to be a completely separate add-in rather than a core component and I hope this is down with OSDM.

Jim,
"I don't want components I don't use becoming part of the application and adding bloat." Absolutely. and we agree. SQL Developer Data Modeling will be a separate standalone product so that users who don't want to use SQL Developer, but who do want to model will have that option. The nice thing about an integrated solution is that if you are doing database work and then want to do some modeling, you are in one tool. Our current plans are to release the standalone product in the initial production release and then follow that with the extension to SQL Developer depending on the customer demand. We do plan to release a read only viewer as part of SQL Developer 2.0. This will be an extension, which like the Migration extension, you can switch off. and from your note, you'd prefer the reverse, that these new extensions are pieces you choose to include and not choose to exclude.
I'm not certain we'll get agreement on this, but I'll be interested. Just this morning I was updating a thread were the request was for all the pieces to be there working out of the box.
Sue

Same icons for objects in SQL Developer as Data Modeler

Hello,
would it be possible to display the same icons for objects in SQL Developer as Data Modeler?
For example:
- in SQLD a session temporary table has the icon of a table with an X symbol, in Data Modeler it is just a table icon.
- in SQLD a materialized view has the icon of a table with 2 arrows, in data Modeler it is just a table icon.
Joop

Hi Joop,
I think you will find that in Data Modeler's Physical Model tree the same icons are used for temporary Tables and Materialized Views as in SQL Developer.
David

Sql Developer and Data Guard enabled instance

I have version 1.1.2.25 SQL Developer and when I try to connect to Oracle 10gR2 instance which is data guard enabled and its logical standby it spits few message, and then connects, but data is not visible from any table.
Is there any way to see data and other code while in logical standby instance which only in read only mode?
Thanks.

This problem came when I tried to connect to Oracle
instance which is a logical standby in data guard
setup. Eventually connection is made and then you can
not see any object.
In logical standby database its suppose to be read
only and should be available for query.
In TOAD you can see every thing and when you want to
make any change ,it spits an error and wouldn't allow
you to make any change.
My question was, why SQL Developer is not showing the
objects in the list and its contains.Perhaps we could help you if you told us what the error was.

SQL Developer with Data Modeler, No Design Menu Option

Using SQL Developer 3.0.04 Build MAIN-04.34 with Data Modeler. I have created a logical design and wish to forward engineer this to a relational model.
I cannot seem to find the Design Menu option to use the >> Engineer to Relational Model option which is available under the Design Menu on the Stand Alone version of SQL Developer Data Modeler.
Have checked the following locations:
Tools -> Data Modeler
View -> Data Modeler
File -> Data Modeler
Right Click on my Logical Design
I have ensure that all my entities have the Engineer To property set to a valid Relational Model.
Is this a bug or am I missing a menu option / configuration setting?
Thanks in advance for any help
John

Hi John,
you can find ">> Engineer to Relational Mode" button among other buttons for logical diagram.
Philip

How to set naming standards for SQL Developer

I am using SQL Developer version 3.0.04.
In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
Any help in setting such preferences would be appreciated.

Hi,
If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
You can then drag Tables from SQL Developer's Connections tree onto the diagram.
Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
(or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
David

Install Oracle XE, SQL Developer, and Toad on the same machine?

I have been trying to install Oracle SQL Developer, Toad, and Oracle Express on my work computer. Installing SQL Developer and Toad was pretty straightforward, and I was able to browse the XE database with SQL Developer. But after installing Toad, problems started. Toad was using Oracle XE's registry settings to locate ORACLE_HOME and oci.dll. So I tried changing the settings for Oracle XE in the registry. Toad now works, but not Oracle XE. And while I was going through this all, I even had a time when I had Toad and oracle xe working, but not SQL Developer. It almost looks like you can choose two of the products, but not all three.
So, my question to the community at large is "Can it be done?". In what directories do you have each product installed? What environment variables do you have set? Where is your tnsnames.ora? What Oracle registry settings do you have set (namely HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE)?
I can post my current settings, but I've been through so many iterations that these current settings don't really matter that much.
Here are the details I am looking for
Path to sqldeveloper.exe
Path to oracle.exe (for Oracle XE)
Environment Variables
ORACLE_HOME
ORACLE_BASE
TNS_ADMIN
PATH (just the oracle stuff)
Registry Settings
HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE\ORACLE_HOME
HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE\ORACLE_BASE
HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE\TNS_ADMIN
HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE\OLEDB
HKLM\SOFTWARE\Wow6432Node\ORACLE\KEY_XE\ORAMTS_CP_TRACE_DIR

I don't use toad, but there should be no reason why you can't install all 3. SQL Developer is a very clean install and affects nothing else. It doesn't add to the path, or create any registry entries except for file associations.
A toad installation should pick up your oracle client (in this case the XE code). I am curious as to why you felt you had to change registry settings. What problem were you trying to fix?
My recommendation would be to uninstall everything, clean the registry and reinstall in the order XE, Toad, SQL Developer. Test in between installations and seek help for problems as you find them. Bear in mind that this is the forum for SQL Developer. QUestions about Oracle XE would be better answered in the dedicated forum, or in the Installation forum, and questions about Toad in a toad forum.

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
   NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
   to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
   a. Sorting (click on column header) and
   b. Filtering.
   c. Copying to Clipboard via right mouse click sub menu of:
      - Geometry's SDO_ELEM_INFO array constructor.
      - SDO_GEOMETRY constructor
      - Error + validation string.
   d. Access to Draw/Zoom functions which were previously buttons.
   e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
      it can process - along with the ring / element that is host to the error (if it can) - and displays
      them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
      The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
   f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
   g. Table now has only one primary key column, and has a separate error column holding the actual error code.
   h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
   i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
   Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
   - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
     option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
     could be shown as: <25> or {x,y} or <25> {x,y}
   - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
   - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
     edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
   - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
   rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
   * NONE
   * START    - All segments of a line have the arrow positioned at the start
   * MIDDLE   - All segments of a line have the arrow positioning in the middle.
   * END      - All segments of a line have the arrow positioning in the END.
   * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
   For geographic/geodetic SRIDs distances are currently shown in meters;
   For all SRIDs an attempt is made to "adapt" the scaleBar units depending
   on the zoom level. So, if you zoom right in you might get the distance shown
   as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
   to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
   click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
   executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
   adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
   added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
   automatically adds a field that holds a unique row number.
3. When exporting to KML:
   * one can optionally export attributes.
   * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
   * If a column in the SELECTION or table/view/Mview equals "name" then its value is
     written to the KML tag <name> and not to the list of associated attributes.
     - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
   in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
   Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
   Example:
   SELECT a.geom.sdo_point as point
     FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
             FROM DUAL) a;
   SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
     FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
   than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
   the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
    However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
    Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
    to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
    Please read the Oracle documentation on how to project your data is this is necessary. An example is:
    SELECT OBJECTID,
           CODIGO as name,
           NOME as description,
           MI_STYLE,
           SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
      FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
    circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
    to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
   types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
   Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
   and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
   in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
   a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
   has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
   what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
   and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
   In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
   right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
    has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
    index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
    which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

Release date for SQL Developer 1.1?

Is there a release date for SQL Developer 1.1? According to your "SQL Developer Statement of Direction", it is due some time in the second half of 2006, but I haven't seen any firm dates. Any update on this would be appreciated, as it is much anticipated.

When the time comes, will you provide us with release candidates or betas like you did for SQL Developer 1.0?
I so look forward to test-driving 1.1 out for a spin. :-)
Eagerly waiting,
Daniel

Report locale, subtemplates and Data Model

Hi,
I have the following situation:
We have 4 templates according to language, with french the default language:
- FR: template.rtf
- NL: template_nl.rtf
- DE: template_de.rtf
- EN: template_en.rtf
The report locale is enough for BI Publisher to select the correct template, so that's OK.
Some data from our database is also based on locale (eg street names and cities).
Question 1: is it possible to use the current locale as parameter for the (sql) data model in some way (eg by using a specific parameter name)? For now we set the report locale to the correct language AND we send that same value through as a parameter. It would be cleaner to just set the report locale and be able to use that value in some way.
Question 2: all of the above templates have a footer that's being reused, each also share the same data model, but the data is again based on the current locale.
so: footer.rtf, footer_nl.rtf, footer_de.rtf and footer_en.rtf. Do I need to import all of these in their respective files or will localisation work (I doubt it)?
Question 3: Is there a way to implicitly pass all parameters that were passed to the main template, also pass to the subtemplates? (eg LANG parameter is passed to template_nl.rtf, who can use it in his data model, is there a way to automatically make LANG available for footer_nl.rtf's data model or do I need to explicitly pass it as a parameter in the <?call-template: footer?>) - again if the report locale is available in some way to the data model, it would be easy.
Thanks in advance

Hello,
Probably the easiest would be to use an OnDemand Process and some AJAX to pull your data into the extjs object.
Here's an example of an OnDemand Process.
http://apex.oracle.com/pls/otn/f?p=11933:11
For data the easiest at the moment would be probably to use the Oracle XML functions to generate your data in XML and use that as your data feed.
You might want to take a look the new Interactive Reports included in APEX 3.1, while extjs has alot of functions there is a bit of setup involved , while the Interactive Reports all you need is a SQL query http://www.oracle.com/technology/products/database/application_express/html/irrs.html
You should search the forum for extjs as there has been quite a few successful integrations of APEX and extjs / YUI / jQuery etc.
Regards,
Carl
blog : http://carlback.blogspot.com/
apex examples : http://apex.oracle.com/pls/otn/f?p=11933:5

Support of PL/SQL Functions in Data Modeler

Hello,
Sorry if this question has already been answered, I searched the forum but got 215 hits on data modeler + pl/sql functions.
So my question is:
Stored Procedures are already supported by the physical model (11g) of data modeler, but I could not find any method
to create pl/sql functions via data modeler - neither in the documentation nor on the user interface. Is this
currently not supported?

Is this currently not supported?There will be support for functions and packages in next release.
Philip

Re: GeoRaptor 3.2.1 Released for SQL Developer 3.x

Hey,
Referencing this that was posted in early September 2012:
GeoRaptor 3.2.1 Released for SQL Developer 3.x
I am supporting GRE's and the like at UC Berkeley and I really want to hook them up with this plug because it will make their life MUCH easier. But I have some pretty basic problems:
1. A VERY simply table that has an 8307 linestring. The query that GR defaults when the table is added :
SELECT rowid,"ID","NETWORK_ID","BEG_NODE_ID","END_NODE_ID","LENGTH","SPEED_LIMIT","DETAIL_LEVEL",
"IN_SYNCH","CREATED","MODIFIED","CREATED_BY","MODIFIED_BY","MODSTAMP","NET_GEN_ID",t.GEOM as GEOM
FROM VIA.LINKS_HOLD t
WHERE SDO_FILTER(t.GEOM,?,?) = 'TRUE'This seems to do something but nothing is ever displayed. The table definition is as follows:
CREATE TABLE LINKS_HOLD (
ID NUMBER,
NETWORK_ID NUMBER,
BEG_NODE_ID NUMBER,
END_NODE_ID NUMBER,
GEOM MDSYS.SDO_GEOMETRY ,
LENGTH NUMBER(9,3),
SPEED_LIMIT NUMBER(3,0),
DETAIL_LEVEL NUMBER(3,0),
IN_SYNCH NUMBER(1,0),
CREATED DATE,
MODIFIED DATE,
CREATED_BY VARCHAR2(30 BYTE),
MODIFIED_BY VARCHAR2(30 BYTE),
MODSTAMP TIMESTAMP (6),
NET_GEN_ID NUMBER
)And some sample data. I am only including the geometry
GEOM(SDO_GTYPE, SDO_SRID, SDO_POINT(X, Y, Z), SDO_ELEM_INFO, SDO_ORDINATES)
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18477, 34.02929, -118.18156, 34.02932))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18268, 34.02393, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18268, 34.02393))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18387, 34.0273))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18387, 34.0273, -118.18257, 34.02731))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18269, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18269, 34.02631, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18131, 34.02632, -118.18256, 34.02631))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18256, 34.02631, -118.18131, 34.02632))
SDO_GEOMETRY(2002, 8307, NULL, SDO_ELEM_INFO_ARRAY(1, 2, 1), SDO_ORDINATE_ARRAY(-118.18257, 34.02731, -118.18256, 34.02631))Since the query I tried to substitute for the system generated one was:
select geom from links_hold ;When I tried to run that the system responded with and error and pasted the following into the clipboard:
SELECT rowid, GEOM as GEOM FROM (
select
rowid,geom
from
via.links_hold
? MDSYS.SDO_GEOMETRY(2003,8307,NULL,MDSYS.SDO_ELEM_INFO_ARRAY(1,1003,3),MDSYS.SDO_ORDINATE_ARRAY(-180.0,-165.78279266572636, 180.0,165.78279266572636))
? Please keep in mind that very same query will display all the links where I run in the generic map view (GMV) of SQLD and
since GMV has little in the way of additional features it is rather frustrating to see your tool not really working, or what
is more likely is that I have a lack of understanding because I cannot find documentation that will allow me to
move forward w/o bugging you.
So Any light you can throw on this would be of great assistance. Thanks much!

Flying Guy,
The non-display is a major bug that was discovered after GeoRaptor 3.2 was released. I knew it was there a few days after
the release - it got past our testers as well. I hoped to have a release out very soon after but a bunch of things conspired to
stop this from happening. Anyway, no one complained so I figured no one was using it enough to find the bug.
The bug is fixed which you can test if you download the Early Access release from our SourceForge website.
There are some other new functions in this EA that you might discover. The main one being the ability to have a feature count
(those drawn within the map window) displayed on the view / layer tree. See GeoRaptor preferences. Another is the restoration
of right mouse click menus on the sdo_geometry columns of table/mv/view connection nodes. Also, if a table has more than one
sdo_geometry column, the first is no longer selected if you right mouse click/map etc on table node. It will display a pick list
of sdo_geometry columns for you to chose from. (There has also been a major revamp of connection management as I noted
problems since SQL Developer 3.2.)
Please download and try it. Consider joining the GeoRaptor lists to help with testing and documenting. If you find bugs in
the EA please email the right georaptor list, or use the GeoRaptor SourceForge site to register the bug. Or email me
directly simon at spatialdbadvisor dot come.
I hope to have a release ready by the end of the week but I have not heard back from the small group of testers
that we have something that is ready to go.
Wrt documentation we have added some where users have created some for me with my input. Please volunteer to
create documentation.
The simple fact of life is that:
1. GeoRaptor is downloaded by lots and lots of people (a good thing).
But:
<complain>
2. Very few responses ever occur to postings made about GeoRaptor on this forum or on our sourceforge forum: disheartening;
3. Very few bug reports or enhancement requests ever get created at sourceforge: disheartening;
4. I have become the only developer which is a bad thing. I known of some Java developers who have used GeoRaptor but
most/all expect someone else to fix bugs or develop the tool. I have spend thousands of hours on a tool that I find useful because SQL Developer
is my main Oracle access tool. But I have never, ever heard from more than 10 people over the past 3 years that they too find it useful: disheartening;
5. Attempts to contact downloaders routinely fall on deaf ears or fail: disheartening;
6. Requests for documenters, developers, testers are ignored or fail because we can't contact anyone who downloads GeoRaptor: disheartening.
</complain>
Like a lot of open source projects I do not get paid for anything I do. But what annoys me is that no one - other than a tiny brace of people - will help with anything
even when we ask.
I have also decided that major new functionality added to GeoRaptor eg GeoRasters; WMS; WFS; etc will only be done when sufficient funding, via a fundraising website
makes a set amount. This is something that the PostGIS have started doing and I think it only fair considering how many months each year I spend on development "in
the dark" for no income.
regards
Simon

SQL Developer and Windows XP Profile space

I work in a secure environment where my laptop is fairly tightly controlled. In particular all laptop users are restricted to a Windows user profile space of 20Mb. This is space in C:\Documents and Settings\<username>\Application Data. This is to stop people building up huge profiles that take an age to download and synchronise with the logon servers.
SQL Developer writes stuff in this directory (as does the Data Modeler and JDeveloper). In particular windowinglayout.xml is growing and is now 1Mb in size. I am running out of space in my profile and it will not be long before I am at my limit. The size of the file seems mostly to be down to the content of the element /LayoutInfo/clientLayoutData/global/view-data which has grown enormous. Much of the content seems to relate to connections and folders and I have tried to delete some connections but that seems not to have made any difference to the size of the file.
Can the content of this file be controlled? Is it possible to relocate these files somewhere else so that they don't cause me a problem? Are there other possible solutions?
Thanks in anticipation.
Andrew

Marvellous K, thanks for that. Not only have I done that for SQL Developer but also managed to work out the appropriate files to amend for JDeveloper and SQL Developer Data Modeler. My profile now has a whole 5.5Mb free and my laptop is a happy bunny again.
Combined with finding where my new 11g database laptop installation has squirrelled away it's alert log I think that's enough productivity for one day; my work here is done.

View jobs with SQL Developer and export to file with delimiter

Hi,
is there a way to view, create and alter my database jobs with SQL developer?
And is it possible to export tables, views or simple queries to file delimited different from the CSV standard?
Diego.

Hi and Welcome to the Forum!!
To select data from a table or a view you must use the SELECT sql command. Example to get the data from your view you can
select ZMATNUM,ZMATCUR,ZMATATTR from ZMATERIALAs you have said you are using SQL Developer just execute the above query in your sql developer and it will show the data. Right click the grid and export the data to excel file.

Forum for SQL Developer and Data Modeler?

Similar Messages

Maybe you are looking for