Numeration of releases of the SQL Developer

Why the updates of the SQL Developer are jumping as many numerations (# 1184 - #1215 - # 1343)?
Our developers until can use releases internal with 'pierced' sequence, but releases of our products that are set free possesss correct sequence.

These numbers correspond to our internal builds, so we are on our 1,343 build. The actual product version is:
1.0.0.13.43
I agree it would be easier to deal with 1.0.0.1, 1.0.0.2, etc. We will see what we can do.
Mike

Similar Messages

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

How 2 find the "Requests from the SQL Developer Exchange Included" in 2.1.1

Hi,
I would like to explore the new features from 2.1.1
http://www.oracle.com/technology/products/database/sql_developer/files/BugsFixed_v211.html
But can not find them in:
http://apex.oracle.com/pls/otn/f?p=42626:46
Where are they explained...?
Thanks, Juergen

Thanks K,
good hint with the filtering of the status...!
I was just wondering if you can find the ID's. When you scroll to the end on: http://www.oracle.com/technology/products/database/sql_developer/files/BugsFixed_v211.html
there you find the section "Requests from the SQL Developer Exchange Included" with a lot of IDs...
8411043 : Commit confirmation
8755723 : Copy column name to clipboard (ctrl - shift- C)
8487257 : Do not use ora_rowscn (Request implemented using a preference)
but the filtering is good for me too...
Juergen

Questions about the sql developer 2.1

first sorry for my poor english, I am very happy to see the sql developer 2.1.but here ,it has a very serious problem.
usually, I used to saving some common sql statements into a sql file. and when need to do something , I just need to open the file with oracle sql developer, and excute the sql statements.
but when I do this with sql developer 2.1, the excute sql button is not activated , the icon is gray ,so I can't excute any sql statement in the file, and I should open a new sql worksheep and type the sql statements to excute it. what's the matter?
thanks!

When opening a script, sqldev logically doesn't know under which connection you want to run the statements.
Just select the connection you want using the drop-down box in the upper right of the script tab's toolbar, and all buttons will get enabled.
Have fun,
K.

Where is the SQL Developer download for Linux

Can some one help provide a URL link to download the SQL Developer for Linux? The official link on the Oracle Website is pointing the Windows zip instead.
Many thanks!

The link is correct. The files are the same for linux and windows when the jre is not bundled.
Eric

Error While Unzipping The Sql Developer

Hi All,
I am facing an error when trying to unzip the SQL Developer ,
Unspected End Of Archieve.
Please Help ...

Thanks for reply.
I re-downloaded and its working now.
thanks alot
parry

Logging/viewing SQL statements generated by the SQL Developer IDE?

I know it is possible to view the SQL statements that the SQL Developer IDE generates to fetch result-sets from the database whenever one performs any action - say expanding the "Tables" node for a database, for example. I would appreciate if someone could point out how this functionality could be enabled.
Thanks,
RG

In 1.0, you could use the AddVMOption -Daudit.trace=db_api option inside the sqldeveloper.conf file.
In 1.1 however, I don't get output inside the console anymore (for expanding trees, etc.).
Kris, has this option been replaced by another one? Please let us in on all the fun ;-)
K.

30EA1: 2nd instance of the sql developer delivers no query results

Hi,
the first instance works like expected, the 2nd one doesn't delivers any result in queries and in the Messages i found that Error:
SEVERE 43 0 Error while registering Oracle JDBC Diagnosability MBean.
best regards
Werner

hi,
well - the main reasons have been already discussed; another intresting one
(i don't know if somebody else was already running into it): sometimes i start e.g. a long running pl-sql block in the window
Then i go back to e.g. the code editor to take a look on another part of the code which i want to edit - then the sql developer freezes
(i think because something is executed through the main connection - and unfortunatly the main session is already executing something)
When the pl-sql block is finished i can use the sql developer instance again; but in the meantime i need another instance
in my regular work i use 3-4 instances of the sql developer
(like mentioned above - to prevent myself by modifying the productive db during i am working on the
development one in the same schemas, to work on another topic which a customer asked me without loosing my old work or because a window freezed)
Here an idea (i know - maybe it is dirty) - the sql developer could open always 2 connections - one for the communication of the tool to the database (which can't be used by a window)
and one for the window (sure - i am aware that i can open an unshared connection window, but sometimes i just forget to do that)
Another benefit of that: currently a lot of statements are sent through the connection - if i want to trace something i have to do it in the sqlplus because these statements are messing up my trace
however - i took a look into the new version and i am quite impressed, a lot of new cool features
best regards
Werner

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

In the SQL Developer how to set Indentation in preferences?

I am using SQL developer version 1.5.1 BuildMain 5440. In the Tools --> Preferences--> Database --> SQL Formatter --> Alignment and Indentations, I see Indentation on the right panel which shows drop down and spaces, and there is a check box option "Use tabulator". It is disabled for me. How do I make that enable? I want to use this in my formatting.

You need to disable the first option "Right-Align Master Keywords"..

Congrats to the Sql Developer Team! The Migration tool is SUPER

Just wanted to say "thank-you" for such a great tool. Last week, I was fighting a third party software / MS SQL 2000 database. Finally enough was enough, boot up Sql-Dev, migrated everything from MS SQL to oracle...extracted the data....baba boom baba bing..boss is happy!
Keep up the great work!

I know that the Spatial and Graph folks have an updated extension in the works for SQL Developer, but I can't speak about particular changes or updates. You could cross post to the Spatial forum as well
Spatial
As per your request for 'shared queries' for your students - I think that's a request independent of our Spatial support, yes?
Could you elaborate a bit on exactly what you'd like to see here?
Our Reports feature has a 'Shared Reports' interface that might get you what you want. There's also Code Templates and Code Snippets as well...
Jeff

Problem with getting started with the SQL Developer in oracle 11g

I downloaded the oracle 11g from the oracle site and installed it on my machine.Now i want to write the sql queries and practise them......so i tried this:start\oracle11gHome\ApplicationDevelopment\Sqldeveloper . But I get a messagebox with a browse button asking me to "Enter the full pathname for java.exe"
what is this all about?Do i need to install jave in my host machine?
how to solve this problem?

hi
If you are asked to enter the full pathname for java.exe, click Browse and find java.exe. For example, the path might have a name similar to C:\Program Files\Java\jdk1.5.0_06\bin\java.exe.
http://download.oracle.com/docs/cd/E10405_01/doc/install.120/e10407/install.htm
hope this helps
zekeriya

SQL Developer create wrong SQL for creation of Database link

Hi,
I tried to create Database link to another machine through SQL Developer. and I got error message saying "Sql not properly ended" or similar.
I copy-paste the sql to sqlplus shell and I found that the problem came from password part of database link so the generated from SQL Plus is something like:
SQL> CREATE DATABASE LINK mytest CONNECT TO anotherDB IDENTIFIED BY 1234 USING 'OtherServiceName';
but it should be
SQL> CREATE DATABASE LINK mytest CONNECT TO anotherDB IDENTIFIED BY "1234" USING 'OtherServiceName';
so if I type in the password field
"1234" which is ****** /6 chars/ the database link was created correctly.
Could you check and fix this in next release of the SQL Developer?
Otherwise the Application is very good and far ahead from TORA :)

Thanks, I didn't notice that for passwords. So it's most definately my problem that the SQL Developer . :)
Thank you for clarification!
Offtopic: I am searching for DB Comparison tool which could compare 2 schemas and return me the differences and the sync script. Do you know any /free if possible/? There is such thing in TOAD but I am on Linux and I prefer to use something else. :)
Thank you in advance

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

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

Numeration of releases of the SQL Developer

Similar Messages

Maybe you are looking for