SQL developer : scroll mouse?
Dear contributors,
I am a newbie in Oracle. My main area now is Oracle Spatial. I recently installed Oracle SQL Developer v1.2.1.
My question is why it does not recognize my scroll mouse ?
Many thanks in advance.
=damon
First of all Satish is right ;)
Secondy: There are many places where scroll mice don't work. You either have to install the software/driver given by the hardware manufacturer or there is a small application called Freewheel, you can try that. It will make your scroll mouse work everywhere.
Cheers, Sidhu
Web: http://www.amardeepsidhu.com
Similar Messages
-
Hi,
I have this problem. I open some table in SQL Developer, scroll in the middle, put focus on some cell or entire line. Then I open another table in another tab. Then switch back to the first tab. The focus is still as it was before, however the table is always scrolled to the first line.
This happens everytime when I switch to another table tab, so I need always to scroll back. When I switch e.g. on another package and then back, the scroll position is correct...
Is there any workaround or bug fix. It is really annoyng...
Thanks, DanWell the carret position is preserved even when you scroll down with a mouse and than click some cell or select entire line. Only the table is scrolled back to the top...
Lets hope they will fix this soon together with dozen of other bugs.
To mwickham:
I use pin by default, otherwise new table would open always in the same window... -
Mouse moving issue in sql developer 3.2
Hi,
I'm using sql developer 3.2 in vmware .I'm facing issue when i try to select the package/procedure from left side tree structure with mouse,mouse pointer is moving to some other place.
If i try to click on one object name(procedure/package/function) then mouse pointer is moving to other object name automatically.It is very difficult to work .Can some advice why it is ? And how i can resolve?
And at the same time no issue with sql developer 1.1 .
Environment:
In side vmware
Os:Xp
Sql developer Version 3.2.20.09Enable security descriptors = Allow virtual applications full write permission to the virtual file system.
Here is how it looks like:
https://twitter.com/packageologist/status/462180503995813888/photo/1 -
Sql developer query window corrupting on scroll
Hi there
I have a weird error - when I scroll in my SQL developer query window (tab) the text corrupts and only comes back if I click in the window somewhere or save. Has anyone else seen this? I'm on version 1.5.5 and don't really want to upgrade to the latest as I don't like the new layout (no dbmsoutput etc in the results window)
Cheers, Katesorted it by adding a line AddVMOption -Dsun.java2d.noddraw=true to the sqldeveloper.conf file, as per thread SQL Editor not refreshing after scroll on Windows Vista
-
Top 10 Obstacles to Sql Developer Becoming a World-class Tool
I've been working with Sql Developer day and night for the last 6 months.
On a positive note, the SqlDeveloper team has been the most responsive Oracle product team I've worked with in the 19 years I've been working with Oracle tools. They pay attention to their customers. It's noticed and much appreciated!
I thought I would share the biggest problems that I face with the tool on a daily basis, the kind of problems that make me want to work with a different tool each and every day.
My intent isn't to gripe, it's to focus attention on the biggest productivity drains I face using the tool. Others may have a different list, based on their needs. Without further ado, here is my top 10 problems list:
1) Quality Control.
I cannot count on critical portions of the tool working correctly. This includes an oracle database development tool that is incapable of extracting oracle ddl correctly and which is incapable of correctly displaying information about SQL Server data and database objects. It also includes destroying connection files and losing keyboard settings. When the product was installed, it was incapable of properly displaying code in a worksheet when I scrolled thru the code. The details are listed in other postings of mine.
2) Quality Control.
See #1.
3) Quality Control.
See #1.
4) Very badly done threading.
The tool locks up on a constant basis when it does a many tasks. Rather than let me work on some other task, I have to wait for it to complete. My current work-around is to have two or three sql developer windows open. That sucks life out of my RAM supply, but at least I can get some work done. And, of course, it will often completely lock up and never return, which means I lose all unsaved worksheets. This forum is full of postings about these issues.
5) Memory Leaks / Internal memory corruption.
If I've had the tool open for a few days, or really worked it hard for a day, I will get bizarre compilation errors that make no sense. If I exit the tool, re-enter the tool, and compile the exact same code all will be well.
6) Awkward and slow data entry interface for frequently performed tasks.
Example: I create a new table and want to start defining columns for it. I remove my hands from the keyboard to press the + button, then I have to set focus on the column name field (it should do that for me!). Now that my hands are back on the keyboard, I have to backspace the dummy "column name" value in the column name field (it should ditch that dummy value for me). Only after all that can I actually enter a column name. When I want to add a new column, it's back to the mouse again, for the same drill. The down arrow key should take me to a new column record, as should pressing return at the end of the last field in the column row.
7) Destroys code
Changing a column datatype from varchar2 to nvarchar2 destroys the length of the column. Changing a field on a view destroys the instead of triggers. This is bad. There is no warning that this this is about to happen, which would at least give us a chance to avoid the problem. Better still, of course, would be not destroying that data.
8) Inaccurate checking for record locking.
When I try to edit records in a data grid for a table, I often get an error message telling me the data was modified in another session. It is simply not true. A hand-written update statement in a sql worksheet will work just fine. I've seen posts in the forum discussing this issue. An Oracle database development tool unable to reliably update oracle data tables is embarrassing. See Obstacle #1.
9) Unicode support
Sql Developer is heads above all the other tools I've tried out on this topic.
However, the configuration of the tool to provide unicode support needs to be simplified.
The tool needs to recognize the encoding of the files that are being opened up. On Windows Vista, Notepad seems to infallibly pick the right encoding for the file when I open it. Sql Developer should do the same. Files have specific encodings, the tool should have a default encoding (that I can override). Right now, the tool has a specific encoding and expects all files to match it. Extracting ddl to a worksheet does not respect the encoding choices of the tool, either. It only works with a limited set of tool encoding choices.
10) Resources
Does the sql developer team have the resources they need to compete with vendors like Microsoft? One really big reason for picking sqlserver over oracle is the ease of use of the Microsoft front-end tools. It's not until later that they may realize that Oracle has more capability, but that's still a lost sale.We are acutely aware of quality and with each release work at improving this. Providing a polished, professional and ultimately user friendly and useful tool is our constant goal.
The broader our customer base grows, the more demands we have. This is a good and exciting position to be in, although it might mean that we need to slow down on our release cycles.
Release 2.0 should address more of the threading and memory leaks displayed as the team have rewritten some of the sections. As for resources, it's true we're a small team and we get on with the work that we do.It might be a little slower than some would like, but I'm not convinced that having large team is necessarily always the answer.
As ever, some of the points mentioned could be added to the Exchange. We'll be reviewing and updating the Exchange again in the New Year.
I think there is another point to add to your list. A lot of what the tool is and will become is from a positive customer interaction we have had to date. While we continue to grow this, I think the product will grow and improve. The forum and all the positive interactions that happen here are key to taking the product forward.
Regards
Sue -
Serious UI issues in SQL Developer 4.0 for Mac
I've encountered some serious UI issues in SQL Developer 4.0 for Mac (4.0.0.13) that impact it up to the point where it becomes unusable.
If the database and tables are expanded in the "Connections" view, sometimes a node in the tree seems to become sticky. Whenever you scroll the up or down, it will immediately scroll back to make the old selection visible again. If you want to work with an item that's outside the current view (e.g. to collapse the "Tables" node), you can no longer use it. SQL Developer needs to be restarted.
If the context menu is opened (ctrl click), it appears in the wrong place. It's too far to the right and bottom. If you then move the mouse pointer towards the menu, a rectangle appears and follows the mouse pointer as if you had initiated a drag and drop operation.
If the "Data" tab of a table is selected and if a cell is clicked to edit the cell value, the text cursor is drawn in the wrong position. It can be off by more than one character and it is often drawn in the middle of a character instead of between two characters. It's hardly possible to edit the cell value as you cannot tell for sure where insertions and deletions will happen. You basically need to copy the value into a separate editor, edit it there and copy it back.
The scrolling in the "Data" tab of a table is a pain. For no obvious reason, it first scrolls downwards a few rows and then jumps to the top (at least using a Magic Mouse). If all rows have been loaded, this problem seems to disappear. But generally, the scrolling distance is far too short. With a long finger swipe, one would expect to scroll the contents by several pages. However, it only scrolls about half a page. For shorter swipes, it's similar. It sometimes only scrolls by a few pixels.
Am I the only one to experience these severe problems? Or is the Mac version not as mature as the Windows version yet?In terms of diagnosis, perhaps not -- probably very time-consuming to debug. I did find some unpublished bugs against dual monitor use ...
Bug 13727841 - FORUM: 64BIT WIN7 SOME DIALOGS SHOW ON DISPLAY 1 WHEN SQLDEV ON DISPLAY 2
Bug 18504928 - NEW CONSTRAINT UI MENU IN TABLE DIALOG AT WRONG LOCATION ON DUAL MONITOR
The first turned out to be an issue in the 64-bit Java AWT libraries, not the 32-bit libraries, and specifically for Windows 7 as opposed to, say XP, but this was all quite a bit in the past and was fixed for 4.0. The second one (on 64-bit Linux), however, just came in yesterday, so you can wait to see if a fix for that also covers your situation or, if you are able, pursue it directly with Oracle Support. -
Help debugging SQL Developer extension
Folks,
JDeveloper 11.1.1.1.0
SQL Developer 2.1.1.64
I am working on enhancing an existing extension and am having problems.
I have a Menu.java class that does this:
package org.GeoRaptor;
public class Menu implements Addin {
public void initialize() {
// Add context menus
XMLBasedObjectAction.registerContextMenus(this.getClass().getResource("menu.xml"));
}menu.xml is loaded as the menus appear correctly when I right-mouse click.
The class that implements the selected MenuAction is:
package org.GeoRaptor;
public class MenuAction extends AbstractMenuAction {
// Action to do at launch
private String action;
@Override
public void launch() {
@Override
public void setArgs(final String args) {
this.action = args;
}The menu.xml reference for this class is:
<?xml version="1.0" encoding="UTF-8"?>
<items xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="dialogs.xsd">
<folder type="TABLE">
<name>Georaptor</name>
<item type="TABLE" className="org.GeoRaptor.MenuAction" classArgs="add_view">
<title>Add to spatial view</title>
</item>
<item type="TABLE" className="org.GeoRaptor.MenuAction" classArgs="create_index">
<title>Create spatial index</title>
</item>
</folder>Whenever I select an action eg add_view, MenuAction.class is never called.
Can anyone give me an idea as to why or how to track down why?
regards
Simon[email protected] wrote:
Thanks but I don't find any SQL Developer forum..1. Go to the OTN forum home page
2. Open the Database link
3. Scroll down until the SQL Developer forum is listed -
Our group is a mid-size technology group who would really like to transition to Oracle SQL Developer from TOAD. However, 2 major drawbacks are forcing many headaches within our group and many people want to switch back to Toad because of these issues, which I think are very minor and could be fixed with the next Sql Developer release.
1. Exporting to Excel! Exporting to .csv cuts off leading Zeros in our data, and just doesn't perform the same way as Excel.
2. Scrolling up and down within the Sql Developer environment. In Toad, you can scroll up or down, and its painful not to be able to do this in Sql Developer.
Any idea if these issues have been considered or being worked on? Thanks so much, we really like the tool otherwise!
Message was edited by:
user493167Yikes. I really don't know. Sometimes the drivers that come with fancier mice don't work on all applications and more generic drivers do. If you did a mouse specific one I would suggest ditching it and going with whatever MS installs automatically. (but you may loose some features) Can't help you much beyond that. The only other thing that I can think of is perhaps using a different jvm. By default it uses 1.5.0_05 and I think sun is up to 1.5.0_08 now. Sorry, but without sitting down at your computer it is very difficult to tell what may be going on. You can also google your mouse name and java and see if anyone else is having issues since it is most likely due to a combination of java and your mouse driver.
Eric -
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 PMThank 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 -
SPEEDING UP YOUR PL/SQL DEVELOPMENT
제품 : SQL*PLUS
작성날짜 : 1997-01-09
=================================
Speeding up your PL/SQL development
=================================
By Jeff Warner
If you're doing Oracle database or application development, then you're probably using PL/SQL. Every PL/SQL programmer is familiar with
using SQL*Plus to develop PL/SQL programs. Developer/2000 offers a better way: Procedure Builder. In this article we'll explore how
Procedure Builder can improve your PL/SQL development.
It has a GUI
==========
The first feature you'll notice in Procedure Builder is the graphical user interface (GUI). Procedure Builder provides separate windows for the
Object Navigator, the PL/SQL interpreter, and the program unit editor. By the way, if you think the program unit editor looks familiar, you're
probably right. Oracle uses it inside the other tools in Developer/2000 (Forms, Reports, and Graphics). Using the Object Navigator, you can
view the relationship between your code and the library and packages. Object Navigator also provides the references and referenced-by
information, as well as giving you the ability to examine the procedures and functions that make up packages and libraries. This makes it very
easy to take advantage of existing code.
The PL/SQL interpreter is just what you'd expect. You can use normal SQL and PL/SQL commands and see the results in the output
window. You create your PL/SQL in the program unit editor window. As with any text editor, you can cut, copy, and paste as well as search
and replace text. You can also use the editor to import and export source files. However, the editor's best feature is the Compile button. Click
the Compile button, and Procedure Builder will compile your code and display any errors in the bottom of the window. Click on the error,
and your cursor will move to the offending line. This will radically improve the compile-debug-run sequence. Speaking of debugging,
Procedure Builder has something that will really make life easier for you.
A PL/SQL debugger
================
Yes, Procedure Builder includes a real debugger for PL/SQL. Its features include breakpoints, triggers, variable inspection, variable
modification, step into, step over, and step out.
Having a graphical and easy-to-use debugger can dramatically improve code development. For example, to set a breakpoint in your code,
simply bring the PL/SQL interpreter window to the front and double-click on the line where a breakpoint is needed.
Once you've set a breakpoint and executed the code, the debugger will stop the program at the breakpoint. From here, you can use Object
Navigator to view and change the variables in the program. To resume execution, you can use Procedure Builder to step into, step over, or
step out of a routine. Procedure Builder also provides an option to simply continue execution.
A powerful feature of Procedure Builder's breakpoints is the capability of adding trigger code. Trigger code is a piece of PL/SQL that
executes when the breakpoint is hit. You can use this feature to log the value of a variable to the screen or a file.
If you need a conditional breakpoint, you can use a trigger. For example, let's say you want to stop execution only if the local variable i is
greater than zero. First, select the line where you want the check to occur and create a trigger by clicking the right mouse button on the line
and selecting Trigger. This will open the PL/SQL Trigger window. In the Trigger Body area, enter the following command to halt execution:
if debug.geti('i') > 0 then
raise debug.break;
end if;
Now the program will stop execution only when this condition is valid. You can also use the Trigger Body of a trigger to log information to a
file or a screen.
Debugging server-side programs
===========================
The version of Procedure Builder shipped with version 1.2 of Developer/2000 is V1.5.5.7.0. Unfortunately, it doesn't allow you to directly
debug programs on the server (this is planned for a future version). However, with the click-and-drag partition feature of Developer/2000,
you can use Object Navigator to drag the program unit from the server to the local program unit and debug it there.
Lots of help
=========
Procedure Builder includes extensive help under Windows. In addition to the normal help available on program features, Procedure Builder
provides help on the built-in packages as well as the PL/SQL commands to maintain libraries, program units, and packages. Also, version 1.2
or later of Developer/2000 provides the Cue Cards and Quick Tour.
Conclusion
=========
As you can see, Procedure Builder is a very powerful tool for development. The debugger is first-rate and the extensive help is a great
addition. One other nice feature of Procedure Builder is that Oracle will license it separately from Developer/2000 if you have users who don't indeed the other parts of Developer/2000. If you're doing PL/SQL programming, you should take advantage of what Procedure Builder has to
offer.micwic --
I logged bug6508875 for this.
One suggestion in the meantime until we can get compile errors directed to the log window for offline objects...
You can open the Database Navigator to point to the same db connection. After generating the offline PL/SQL to the db, refresh the connection in the DB navigator. You will see any invalid objects flagged with an error icon. Then you can right-click on the PL/SQL with the error, and "Make" it. This will display the errors in the log window, similar to SQL Developer.
-- Brian -
Foreign key Mapping based on Data - in SQL Developer Data modeler
Team
Do SQL Developer Data modeler supports Foreign Key mapping based on the Data in the Schema rather defined at the DDL ? For e.g if we implement a Objects Relation ship mapping in Data base, we don't define Foreign keys at table creation.
Toad does this feature through "AUTOMATIC FOREIGN KEYS MAPPING IN TOAD DATA MODELER" more info at (http://toadworld.com/Blogs/tabid/67/EntryId/905/Automatic-Foreign-Keys-Mapping-in-Toad-Data-Modeler.aspx)
any one know how to implement through some scripts also helps me
Regards
RajIf you have table PKs defined and the candidate columns match those PK columns, then you can use the Discover Foreign Keys utility. Right mouse over the relational model name (node) in the left browser. It is about half way down the menu. I did a blog post about it last week on kentgraziano.com.
-
Running a Stored Procedure in Oqacle SQL Developer
Hi All,
Could anybody elaborate on the procedure to execute a Stored Procedure in Oracle SQL Developer. I feel we need to configure the output for the DBMS_OUTPUT
Cheers,
Bellon the procedure to execute a Stored Procedure in Oracle SQL Developer.Select the procedure or package spec in the Connections panel. Right click with the mouse. This will bring up a panel with an anonymous block to run the code and property sheets to populate the parameters, etc.
Cheers, APC -
Oracle SQL Developer freezes and locks up computer randomly
I attempted to find a solution to this before posting. I looked through the first 40 pages of this forum and on Google, through the Developer documentation, etc. with no luck.
The problem: while using Oracle SQL Developer, the computer randomly freezes. Things work, but it hangs too often and for too long to use. This is random - it can happen every 10 seconds or every 2 minutes. The mouse will lock up, and the keyboard buffer will get all messed up. For instance, if it happens to freeze while I'm hitting "backspace", it will delete many lines of text (I've lost a bit of work because of this in the past). The freezing will last about 2 to 20 seconds, and the only way out of it is to ctrl+alt+delete and kill SQL Developer.
If SQL Developer is running, and I'm in a different window - it will freeze the other windows as well. Again, it's impossible to use unfortunately. My coworker doesn't have the same problem, and he's connecting to the same database with the same version using Windows Vista. It must be something on this computer. I reformatted about 1 month ago, so it's a pretty fresh install and I haven't installed much of anything yet.
I'm using Windows Vista Enterprise 32-bit w/SP1.
This was occurring with older versions of SQL Developer (1.2). I'm using the newest install that included the Java JDK. I've completely removed Java, my Oracle installs, and a host of other attempts to fix this, and nothing changes. I've tried running the .exe in the bin directory as administrator as well.
Currently using Oracle Developer 1.5.1.54.40.
Any ideas?I tried dumping the contents, but the java dump wasn't showing anything at all, and it would never freeze while I had the console window in focus, so it wasn't very helpful unfortunately.
I fixed this issue by uninstalling the Java runtime on this machine and installing the Java JDK 6 Update 7 from java.sun.com/javase/downloads . I then downloaded the SQL Developer 1.5.1 version without the Java runtime included, and pointed it to the Update 7 .exe file upon first load.
I was using JDK 6 Update 6 previously, and it must have been behind the errors. Note that the Update 7 has to be downloaded from that website as it's a new version that hasn't been posted on the regular java.com site yet.
Message was edited by:
user645599 -
Problems using Quick Migrate in SQL Developer 1.5 for MySQL to Oracle 10g
Hi all,
I am trying to use SQL Developer 1.5 migration tools (Quick Migrate) to perform online capture and build source model to migrate from MySQL 5.x to Oracle 10g on Windows platform. I get these errors and the Quick Migrate process fails:
oracle.dbtools.metadata.persistence.PersistableObject.doInsert(PersistableObject.java:238)
I did a search and used the sqldeveloper.cmd script but still fails. Then I created a new database and truncated the repository. I now get the above error plus two new ones listed below:
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
Error loading nls:OALL8 is in an inconsistent state
Error occurred during capture: Protocol violation
It fails during the capture process for MySQL 5.1 database
when it begins to capture the tables from MySQL.
Does anyone know how to resolve these issues when migrating from MySQL to Oracle 10g using Quick Migrate with SQL Developer 1.5 release?
Regards,
Ben Prusinski
Message was edited by:
benprusinski
Message was edited by:
benprusinskiHi all,
I put the following in my sqldeveloper.cmd file:
SET ORACLE_HOME=%CD%
What is very confusing is that with SQL Developer 1.5, there are several levels and several SQL Developer executables! I am really not sure which of these to use:
I created the SQLDeveloper 1.5 directory called SQLDeveloper1_5 on Windows:
1) cd C:\sqldeveloper1_5\sqldeveloper-5338
there exists a sqldeveloper.exe
2) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper.exe
3) cd c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloer\bin\sqldeveloper.exe
Which SQLDeveloper 1.5 executable should I be using and where should I place the
sqldeveloper.cmd file?
Also I did try to use a different database and schema for the repository with Quick Migrate but it appears a bug exists in SQL Developer 1.5 version that causes errors with Quick Migrate for MySQL to Oracle? Is this correct?
As an update, I ran the following commands:
cd to
c:\sqldeveloper1_5\sqldeveloper-5338\sqldeveloper\sqldeveloper\bin
sqldeveloper.cmd sqldeveloper.exe
Start sqldeveloper.exe
Perform standard capture for MySQL using the new mig2 schema as the new repository
It starts the capture but fails on the errors below:
Error loading nls:OALL8 is in an inconsistent state
UPDATE
============================
I tried this again and it worked with the exception of one error message listed below:
Here are the steps that I followed:
1. Create a Windows cmd script
Put the following entries in the script:
SET ORACLE_HOME=%CD%
save the command windows script as sqldeveloper.cmd
Copy this script to the base installation directory for SQLDeveloper
Example:
1. cd c:\SQLDeveloper1_5\sqldeveloper-5338\sqldeveloper
2. Start SQLDeveloper with the command script that you created earlier
Example:
Open a Windows shell prompt window and execute the following scripts:
a) sqldeveloper.cmd sqldeveloper.exe
b) sqldeveloper.exe
3) In SQL Developer 1.5
From the Migrate menu,
a) Delete current repository and create a new schema in Oracle target database call it mig2.
b) Then create a new repository in SQL Developer 1.5
c) Right mouse click on the MySQL 5.x database and choose capture
It worked with the exception of one error message:
o.jdbc.driver.OracleDriver
Error while registering Oracle JDBC Diagnosability MBean.
So it looks like something is screwed up with my JDBC drivers and configuration for MySQL. How do I diagnose the JDBC driver issue for MySQL?
Thanks!!!
Ben
Thanks
Ben -
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 PMSimon,
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
Maybe you are looking for
-
Creation of TO using 'L_TO_CREATE_MULTIPLE' greater then pallet quantity.
Hello Friends, When we are trying to create a TO (transfer order ) using FM 'L_TO_CREATE_MULTIPLE' for greater then pallet quantity/size of a material it is given me message in u201Cinsufficient quantityu201D. But there are many pallets for the ma
-
How do you display file type in PS Elements 10?
How do you display file type in PS Elements 10 in the Organizer for each photo? I know you can right click and look at meta data. In PSE 7 it was displayed under each photo.
-
C7250 All in one Wireless radio not working
I have a C7250 All in one printer that suddenly the wireless stopped working. I ran the wireless test and it says the radio is on but the radio fails. The wireless LED is on, any suggestion on what could be the problem?
-
How to remove unused objects from the webcatalog In OBIEE11g
Hi, I want to delete unused objects from obiee11g catalog, i know in obiee10g it's working fine (i.e: we can do it via manage catalog then delete the unused objects) is there any way to do it automatically like RPD utility --->removing unused objects
-
Hello! Just connected a used iPhone to iTunes for the first time. I'm trying to restore it to factory settings/default. The phone is connected via Wi-Fi and is updated to the most recent OS that the phone allows. The computer is also connected to the