Recent content by timboc

Thanks for the info. Can you elaborate on why this isn't implemented in a Command Window? I'm both a PL/SQL Developer user and a Delphi Developer (using your Direct Oracle Access product, which is amazing). I was just wondering.

Can you show me the syntax I'd use to accomplish the same in a Test Window? Also, is there are reason this isn't implemented in a Command Window? Thanks, Tim

variable x REFCURSOR begin open :x for select distinct location_name from t_location; end; / print x -- works fine in SQL*Plus

It would be nice if PL/SQL Developer remembered the size/position of the file open dialog on future opens. It's a pain to have to resize it every single time I open it. -Tim

CTRL-F (Find) comes to mind as I use it most often.

I've noticed that many of the popups don't center properly when using multi-monitor support under WindowsXP. They end up showing the left half of the popup at the extreme right edge of my screen in which PLSQLDEV is running with the right half of the popup going off the screen (my second...

I think thats exactly what I need, I'll give it a try. -Tim

I guess I could jam my command scripts into a test script, I was hoping to have similar functionality right from within a Command Window. -Tim

Is there an easy way to have PL/SQL Developer stop executing commands if it detects an error has occurred? I often write long upgrade scripts and hate running them a line at a time using the pause functionality. -Tim

I'm seeing it return False for all SQL commands, that's why I grab the return and invert it before testing it. I think this is a bug (that's what I was told when I reported it for version 3.x) but the priority must be really low. When/if it does get fixed I'll just have to remove the line in...

Marco, thanks for the quick reply. Unfortunately my code is not behaving the way you are describing. .Execute is always returning FALSE: bSQLExecute := OracleScript1.Commands[liCSCurrent-1].Execute; LogEvent(OracleScript1.Commands[liCSCurrent-1].Text,false); if bSQLExecute then...

I think this is something I asked about back in the 3.x days. I'm checking the return value from this function to see if an error has occurred. I'd expect that TRUE represent no error and FALSE represent an error. I think the only error that is returned would be that the SQL command couldn't...

It's strange that I'm seeing just the opposite: .Execute is returning False when my statement was executed. I've yet to get a scenario where it returns True. -Tim

What exactly does it mean if the function returns False? The documentation states that "The result indicates if the command has been handled.". I'm guessing that I still have to check the errorcode/errormessage on True or False so I'd like to know what more False means. Thanks, Tim