Recent content by Jonathan Taylor

It would be nice to have option to disable triggers and/or foreign keys.

Sorry, it's under "Keys", not "Checks". I suppose that this makes sense, since the UNIQUE constraint is a combination of INDEX+KEY.

6.0.6.947 Sorry, didn't realise V7 was out....I will try it in V7.

The constraint test_cons can't be seen after the following:- SQL> create table test (x number) 2 ; Table created SQL> alter table test add constraint test_cons UNIQUE (x); Table altered SQL> edit test

Version : 6.0.5.926 the large data editor seems to misinterpret a Unix-style end of line terminator (one character - CHR(10) - LF) as a Windows/DOS end of line terminator (two characters - CHR(10)||CHR(13) CR/LF). create table eol_test (clb clob,vc2 VARCHAR2(20)); insert into eol_test values...

1. Would it be possible to have the option to store password to be on a per-connection basis? I want the passwords for test databases to be stored, but I don't want the passwords for "live" databases to be stored. 2. If you use table->edit data, the "edit data" padlock button is enabled...

If you have a table that has several columns in an index and/or a long storage clause, then use Edit->Indexes - you will see that the window has a scroll bar along the bottom to fit all the information in. However, in this case, the "storage" button is missing. Also, I've noticed when viewing...

Another small point - I think that the "interval" field should support multiple lines (just like the "what" field). This is because I often have quite complicated criteria for interval (such as run at 12PM & 5PM), that includes lots of nested DECODEs etc., which are better formatted over...

If I run the following query SELECT ROWNUM ID FROM all_objects ORDER BY 1 Then PLSD returns 100 rows - with IDs running from 1 to 100. Because these numbers don't need a wide column - the column is sized small. If I then change the "ORDER BY 1" to "ORDER BY 1 DESC", I get the IDs in...

When I open up the Jobs branch, I'm presented with just the job numbers. However, 99% of the time I do not know what the job number is of the job I want to view/edit. Therefore, I have to query USER_JOBS/ALL_JOBS (rather than inspect the properties of all the jobs) to discover which job number...

Could there (or is there?) an option to make any newly opened windows (e.g. SQL Window) default to being maximised? The first window opened in a session seems to open non-maximised - any further windows that are opened seemed to inherit the maximised/normalised property of the current window...

Viewing of BFILEs seems to have stopped working in the latest version (6.0.2.880) - I'm sure that this used to work. Running an SQL like: select dbms_lob.fileexists(bfilename('&dir','&file')) fileexists ,dbms_lob.getlength(bfilename('&dir','&file')) filelength ,bfilename('&dir','&file')...

Case: A query returns 0 rows, and the datatype of one of the columns is CLOB or BLOB. Clicking on "..." button next to the CLOB/BLOB returns an error:- " is not a valid integer value

It would be nice if there was the option to alert the user when a long running SQL or PL/SQL block had returned rows/finished. Since I do other things while long-running PL/SQL is running - this should appear even if the PLSD window is not the current window. Perhaps this could happen when...

When the user clicks and selects an invalid object (such as a package body), the errors for that object are shown in the lower pane. If the user drops the object (right click, drop), then the object is dropped, and the object is removed from the list. The objects below the dropped object "move...