Bug Report: SQL Window

[ScottMattes]

ctl-e shows that the last SQL that I executed was on 11/3, but for the last hour I have been executing SQLs!

The history
I have one SQL window open that shows me all the rows that an Oracle Report will show. This window was from last week when I quit for the week.

Another SQL window shows only a subset of the first (there is an additional AND that uses a &var). This window was also from last week.

I executed SQL window 'one' and copied the unique identifier that I wanted to work with from the result grid, went to the 'another' SQL window executed it and pasted in the unique identifier in the substitution window.

the first couple of times this went well, but on the third time I got an Ora-32255 and the result grid was not displayed, though the toolbar for it was. After finding nothing helpful with google I tried executing again and while the status bar said 'x rows of y' the grid didn't show (only the toolbar covering the entire area).

So, I closed that SQL window and opened another and went to get the last SQL from ctl-e and found that it hadn't recorded ANY of the SQLs that I had run today. In the new SQL window I did a quickie SQL and then ctl-e and that showed up.

To add to this, the last time I had used PLSD (the last date that shows up in ctl-e list BTW) I had killed it so that the SQL windows that I was working with would be there when I started work this week.

 

[ScottMattes]

Is there some limit as to the size of the entry saved with ctl-e? I just noticed that none of the SQLs are saving even after starting a new SQL Window.

The SQL that isn't saving is 101 lines long. IE says it is 6k on disk.

 

[Marco Kalter]

There is indeed a maximum size for SQL statements, which is 4000 bytes. Larger statements will not be stored.

 

[ScottMattes]

ouch! glad I found out now, instead of when I couldn't recover.

I'd like that to be configureable, as much as possible ( 4k, user specified size, all sqls).

I'd also like some visual way of knowing that the current SQL is too big to be saved. maybe display the size and some words/colors in the tool bar on the right of the window?

 

[Marco Kalter]

I have added this to the list of enhancement requests. At the moment you do not get any clue that the SQL is too big for the recall buffer.

 

[ScottMattes]

The LBC Recall Named SQL plugin does not have this limitation, so I'll save my large SQLs there

 

[RobertK]

Is the "LBC Recall Named SQL plugin" still constrainted to 1000 limitation on statements ?