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

Similar Messages

Next Release date of sql developer

Does anyone know the expected release date for the next version of (1.3) SQL Developer? I'm interested in the revision control functionality and hoping to get a general idea of when it will be available.
Thanks

Hi Kris,
Thanks for responding. I understand that dates can't be committed to unfortunately I won't be attending OOW this year and I was just hoping to get a general indication if the update would be this year or some point in the first part of next year.
Thanks, Rick

Street date for SQL Developer 3.0

Does anyone know when this will be released? I saw a neat-o presentation at OpenWorld and can't wait to get my hands on it.

Thanks Sue and Ashley,
I understand that you cannot provide a specific date and appreciate your timely feedback in this forum.
For others watching this thread, Tom Kyte gave an excellent presentation at OpenWorld
where he demonstrated some of the new cool 3.0 features which you can find on his
site http://asktom.oracle.com/pls/apex/f?p=100:8:0::NO. Look for the oow_2010.zip file.
Steve

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

GeoRaptor 3.2.1 Released for SQL Developer 3.x

Spatialites!
After 6 months of development and testing, GeoRaptor 3.2.1 has been released for SQL Developer 3.x (tested on 3.0, 3.1 and 3.2). This release no longer supports SQL Developer 1.x or 2.x releases due to internal changes to the SQL Developer APIs.
GeoRaptor can be downloaded from the GeoRaptor project's sourceforge page: http://sourceforge.net/projects/georaptor and installed via Help>Check for Updates>Install from Local File. Installation via SQL Developer's update mechanism should be available soon.
The release notes for this release are:
* Fixed issues with validate geometry functionality in particular the update dialog box.
* Revamped "About GeoRaptor" form. Includes clickable URLs, links to mailing lists, version number listing, thanks to testers etc.
* Placed "About GeoRaptor" icon on GeoRaptor's map toolbar.
* SQL Developer NLS settings accessed: improvements in the display and entry and numeric data.
-- Tolerances in Spatial Layer properties will display with the NLS decimal separator eg 0,05.
     Some parts of GeoRaptor such as Validation that show and accept numbers have not been changed from when someone else modified the code.
     If you double click on the left MBR/right MBR icon in the map at the bottom, the current centre position will display according to the NLS settings.
     Editing the value to jump the map to that point works even with grouping separators and decimal separators being commas!
* Spatial Layer Draw has been modified to use NLS based decimal formatting.
* New geometry marking/labelling options have been added. In particular you can now label the vertices of a linestring/polygon with the following additional elements:
-- Cumulative length
-- Measure (M)
-- Z value
-- Labelling of vertices with <id>{X,Y} now also honours 3/4D geometries. If geometry has XYY then it will be labelled as {X,Y,Z} etc.
* You can also label each vector/segment of a linestring/polygon with:
-- Length
-- Cumulative Length
-- Bearing (approximate for geodetic/geographic data)
-- Distance (approximate for geodetic/geographic data)
-- Bearing and Distance (approximate for geodetic/geographic data)
* The font properties of the mark text can be changed independently of the feature label. This includes the offset and label position (CC, LL, UR etc).
* New feature labelling options have been provided:
-- First/middle/last vertex,
-- Any supplied sdo_point within a line/polygon's sdo_geometry object, or
-- Calculated by GeoRaptor on the client side using Java Topology Suite.
* Result sets now have the ability to:
-- Copy to clipboard all geometries across many rows and columns.
-- Display one or more (selected) geometries in a popup image window. This functionality is also available in the result set generated by an Identify command.
* New GeoRaptor Preferences:
-- Width and height in pixels of the new popup image window (displaying one or more geometry objects) can be set;
-- Colours of orphan, missing and correct metadata entries for Metadata Manager;
-- Prefixing with MDSYS for all currently supported spatial objects - sdo_geometry, sdo_point, sdo_elem_info, sdo_ordinates, sdo_dim_info - has been made an option.
-- There is now a new property called "Show Number Grouping Separator" in Tools>GeoRaptor>Visualisation.
     If it is ticked a number will be formatted with the thousands separator in Tools>Database>NLS eg 10000.000 will display as 10,000.000.
* Sdo_Geometry display of all spaces in text between elements of the sdo_geometry array have been removed.
   This was done mainly to compact the sdo_geometry strings so that they are as small as possible when displaying or copying to clipboard.
* Help pages added to the following dialogs with more to follow:
-- Metadata Manager,
-- Shapefile Importer and
-- Layer Properties dialogs.
* GeoRaptor menu entries renamed. New "Manage All Metadata" entry added to View>GeoRaptor menu.
* Spatial Index creation dialog now supports additional index parameters and parallel build settings.
* Metadata Manager overhauled:
a. Shows:
     1. Metadata entries which have no underlying oracle object (orphan)
     2. Metadata entries for existing underlying objects (existing case)
     3. Database objects with sdo_geometry for which no metadata entry exists (new)
b. All orphan/existing/missing colours for (a) can be set via Preferences>GeoRaptor>Visualisation
c. All actions for main (bottom) metadata table are in a single right mouse click menu.
     Some entries will only appear if a single row is selection (metadata copy), others (delete and copy to clipboard) will appear for one or more.
d. Can now switch between open connections to modify metadata of other objects in schemas other than the starting object.
e. Buttons revamped.
* Tab/Shapefile export:
a. Export now supports NULL valued columns. Can be exported as an empty string (if DBase override in GeoRaptor Preferences is ticked) or
     as a predefined value eg NULL date => 1900-01-01 (set in new GeoRatptor Import/Export Preferences).
b. Some work attempted on export of NLS strings (still not corrected).
c. Objects with no rows now correctly processed.
* Shapefile Import
-- Bug relating to Linux file names corrected.
* Fixed issue (identified by John O'Toole) with spatial index underlying a view not being used in map display.
* Reinstated sdo_nn as the principal method for Identify (requested by John O'Toole).
* Fixed problem with handling single click zoom in and out in GeoRaptor map etc.
* Fixed problem with rendering lines from database item (identified by Vladimir Pek).The new "About GeoRaptor" should be read by all people installing GeoRaptor.
Please, please consider registering your email address with our private email list so that we can get a feel for the sorts of people downloading and installing GeoRaptor.
Please consider helping us with documentation or the internationalisation via translating properties files from English to your native language.
GeoRaptor is written and maintained by people who use SQL Developer and Spatial every day but we don't pretend we know everything that users want: please let us know via our feature request page at SourceForge.
We don't get paid for what we do so are always looking for additional help.
Here are some of the requests we have had for improvements:
1. MySQL access
2. WMS access;
3. Ability to import shapefile data into an existing table;
4. Ability to processing multiple shapefiles into separate tables (current version can import one or more into a single target table);
5. Ability to export/import layer definitions to give to others;
6. Support for non-English character sets for varchar exports to shapefiles.Some are relatively simply, some require a lot of engineering work. For the latter, we are considering alternative funding methods to the currently completely free development approach.
Thanks to the following for their invaluable assistance:
Holger Labe, Germany
John O'Toole, Ireland
Vladimir Pek, Czech Republic
Pieter Minnaar, Holland
Olaf Iseeger, Germany
Sandro Costa, Brazil;
Marco Giana, Australia.regards
Simon Greener
Principal GeoRaptor Developer
Edited by: Simon Greener on Sep 10, 2012 2:43 PM

Simon,
I will admit, I almost never use SQL Developer. I have been a long time Toad user, but for this tool, I fumbled around a bit and got everything up and running quickly.
That said, I tried the new GeoRaptor tool using this tutorial (which is I think is close enough to get the jist). http://sourceforge.net/apps/mediawiki/georaptor/index.php?title=A_Gentle_Introduction:_Create_Table,_Metadata_Registration,_Indexing_and_Mapping
As I stumble around it, I'll try and leave some feedback, and probably ask some rather stupid questions.
Thanks for the effort,
Bryan

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

To find last updated date in sql developer for a procedure or a function

hi
how to to find last updated date in sql developer for a procedure or a function.
i m using sql developer version in 1.2

I think you are in the wrong forum...
Anyway you can try
select * from
all_objects o
where o.object_type in ('FUNCTION','PROCEDURE');
you have there the created date, last DDL and timestamp

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

ETA for SQL Developer 2?

I'm a little excited. Is there an ETA for SQL Developer 2? Is it soon? :-)

Oracle has a policy that does not permit us to provide specific dates for releases. This is for your protection and ours, as features planned for a release may be moved to later releases. Our release plans had been for the full language translation set to be in SQL Developer 1.5.3. With the full suite of languages taking longer than planned, we released 1.5.3 which included Japanese, and added a new release, 1.5.4 to include the rest. As Kristof says 1.5.4 includes further translations and, like our other releases will include bug fixes. As he is not an employee he has no access to our release cycles, and as such his dates are speculation and inaccurate. We are currently working on SQL Developer 1.5.4 and SQL Developer 2.0 both of which are due for release in 2009.
Sue Harper
Product Manager

Is there a release date for Apple pay in australia

IS there a release date for Apple pay in Australia

The SQL Developer team have always run a series of early adopter releases before the production release as we have found the community really get involved in these, which is of course benficial for everyone. We plan to do the same for the next release and will announce any early adopter releases here on the forum.
We will be demonstrating features at Oracle OpenWorld, but you may recall that SQL Developer 2.1 was not production for that last year, so we have a lot to show.
Unfortunately we are bound by Oracle policy and may not release any dates.
Regards
Sue

Feb 21st release date for PlayBook 2.0 was just confirmed publicly

Feb 21st release date for PlayBook 2.0 was just confirmed publicly by Angel Aldana (RIM Manager Latin America Alliances) during the webcast "Developing Native Games with BlackBerry NdK 2.0".
tick tick tick
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Best Buy showcase:
http://www.bestbuy.ca/en-CA/research/blackberry-playbook-with-playbook-os-2-0/rc8584.aspx?path=eace3...
Future Techspot:
http://www.futureshop.ca/en-CA/research/one-little-tablet-packed-with-the-best-of-blackberry/rc9372....
All get ready for the arrival of OS2.0
TUESDAY MORNING

Statement terminator problems when exporting data with SQL Developer 3.2

I've ran across what appears to be a bug with SQL Developer 3.2.20.09. If someone can let me know if this is indeed a bug, or just something I need to configure differently, please let me know.
The problem is related to exporting a database as a SQL script, and terminator characters at the end of "create" statements, especially when columns have comments, and problems that occur when using SQLPlus to run the export script to create the tables. With the old SQL Developer 1.5.4, with the "Terminator" and "Pretty Print" options checked, statements like the following are generated:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
When I then run the script using SQLPlus, everything works fine. However, with SQL Developer 3.2.20.09, with the same options enabled, the same statements are generated like this:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE ;
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.';
Notice all of the extra slashes in there. If a slash is not used as a statement terminator, SQLPlus treats slashes as a command to repeat the last SQL statement, which causes many errors about tables or sequences already existing. So, I tried removing the "Terminator" flag from the export options. This lead to statements that looked a bit more promising:
-- DDL for Type NUM_ARRAY
CREATE OR REPLACE TYPE "NUM_ARRAY"
IS TABLE OF NUMBER(20)
-- DDL for Sequence MYTABLE_SEQ
CREATE SEQUENCE "MYTABLE_SEQ" MINVALUE 1 MAXVALUE 999999999999999999999999999 INCREMENT BY 1 START WITH 1 CACHE 20 NOORDER NOCYCLE
-- DDL for Table MYTABLE
CREATE TABLE "MYTABLE"
(     "MYTABLE_ID" NUMBER,
     "COL2" NUMBER,
     "COL3" NUMBER
-- DDL for Table ANOTHERTABLE
CREATE TABLE "ANOTHERTABLE"
(     "ANOTHERTABLE_ID" NUMBER,
     "COL2" VARCHAR2(1024),
     "COL3" VARCHAR2(1024)
COMMENT ON COLUMN "ANOTHERTABLE"."ANOTHERTABLE_ID" IS 'This is a comment.'
The big problem, though, is in the statement for the table with a comment. Notice that there are two statements, but there is not a semicolon after either of them. This unfortunately causes the "COMMENT" statement to be appended to the "CREATE TABLE" statement before being executed, which causes the table to not be created (which causes even more errors later on when the script attempts to populate the table with data).
So, it would appear that this is a bug, but I'm not sure. Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
Thanks,
-Bill

>
So, it would appear that this is a bug, but I'm not sure.
>
That would be a bug. Thanks for reporting it and providing the detailed example.
>
Is there a way I can configure the export options to make SQL Developer export these statements like it used to in older versions?
>
No.
Leave the thread open. One of the developers for sql developer should be monitoring the forum and can provide more information.

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

Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7

Hi All
I Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7.
SQL developer behaves weirdly sometimes. It frequently drops connection, doesn;t show compile button when i open a procedure and certain other things.... I found ver 3.0 quiet stable.
I think it may be because of my incorrect java version (1.6.0). Please tell me how can I get this Java version 1.6.0_4. I checked oracle.com, version 35 is available there....
Can you please help me by providing this ?
Thanks

>
I Need java 1.6.0_4 for SQL developer 3.2 64bit, Win 7.
I think it may be because of my incorrect java version (1.6.0). Please tell me how can I get this Java version 1.6.0_4.
Can you please help me by providing this ?
>
No - we can't provide it. You have to download it yourself. If you have trouble with the download you should report the problem to Oracle.
>
I checked oracle.com, version 35 is available there....
>
If you checked at the Java SE Downloads page
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then you should have seen the 'Previous Releases' link jus above the download Icons near the top of the page.
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html#jre-6u1-oth-JPR
All of the available prior versions are available at that link.
But I strongly suggest you heed the advice given to use the latest 1.6 version of Java available unless you have a very good reason not to.

Dell OMSA ViB Release Date for vSphere 6.0

Hi,
is there any information on release dates for vsphere vib's for vSphere 6 (OMSA 7.4.1 / 8.0.1 / 8.0.2)
apart from that... will OMSA 8 be continued in two different development branches for T430/R430/T530/R530/M630... and T630/R630/R730/R730xd or will there be a future single release for all 13G serversystems.
kind regards
Torsten

Toki76,
The Dell Customized ESXi 6.0 ISO was just released 2 days ago. So I would assume, from past experience, that the VIB is going to be released very shortly behind it., but as of right now I don't see it released. I can research to see if I can narrow the delivery date though, and let you know.
In regards to OMSA 8, likely it will be a single version that encompassed both branches.

Release date for SQL Developer 1.1?

Similar Messages

Maybe you are looking for