Standard Query enhancement

[Maxmix]

Hi!

This is useful feature that I use extensively:



However, it could be even more useful!

1) Usually I have to fill in edit boxes 'Object owner' and 'Object name'. But it is error prone.
I can make mistake and never sure should I capitalize identifiers or not. Could you turn plain text boxes into comboboxes? Choosing from (currently visible in ObjectBrowser) items would be nice.

2) Button "Save as Standard Query..." only becomes visible after you executed some query. But in my experience PLSDev saves not single SELECT but the whole contents of SQL pane (which is convenient, again, because I can have several statements, including DML, comments, and just arbitrary text saved as a whole). Then I suggest to relocate button closer to
File | Save as, which should make it clear what exactly will be saved to file and will make it possible to create standard queries without executing them beforehand.

3) Related to 2). If we open SQL Window as "Standard Query" (that is from context menu), then make some changes, then upon resaving the fields 'Query name', 'Object owner' and 'Object name' should be already filled, so that user will not have to specify them again.

4) I could use the same functionality with PACKAGES(pipelined functions test queries, mostly, but other uses are also possible).
That is, if I have some query in form of:

select ... from table(package.function(...)) where ...

then it would be very nice to save it as standard query for the package (not package.function!).
Or, I would tie some complex BEGIN .. END; block to some package (or to standalone proc/func)

In short words, I am requesting regular saving operation, but with filename linked to some top-level DB object.

Feature to supply long human name is very neat, I wish it retained!

 

[Marco Kalter]

Thank you for your suggestions. I have added this to the list of enhancement requests.

 

[William Robertson]

Also while we're at it, could the "Object owner" attribute be a wildcard or nullable? We typically use a standard schema for production and pre-production, let's say 'XYZ', but dev and test environments will be 'XYZ23', 'XYZ24' etc, which rather limits the usefulness of the standard queries.

 

[Marco Kalter]

I have added this to the list as well.

Item 1 has been implemented for the upcoming 10.0.4 release. Item 3 already seems to work as specified.

 

[Maxmix]

Thanks for Item 1, it works!

Item 3 - no, it seems Developer tries to pick up a new table which corresponds to last executed query. That is, writing "should be already filled, so that user will not have to specify them again" I meant "should retain the object schema.name".

Now if I open standard query named AAA defined on the S1.V1 view (whatever text it contains), then I change the contents to
select * from S2.T2 - during saving this query as standard one I will get all filled fields:
Query Name = AAA - correct
Object Owner = S2 - wrong
Object Name = T2 -wrong

 

[Marco Kalter]

We'll check it out.

 

[Maxmix]

Now I would like to be able

1) to see that current window was in fact read from .sq-file. For example, analogous to how window title is read DBMS_Metadata for after I request to provide DBMS_Metadata for a some object, opened .sq file could set window name to "StandardQuery for objectname - ", where - the name I chose for the "query" (in fact, for whole contents of SQL Window) at the moment I created this standard query.

2) to delete a stored query. May be just 'Show in Explorer window' command, so that I will delete myself by means of Windows. Now it takes many steps to seek to the file needed.