Toad World® Forums

Unnecessary question


#1

Hi, this is a minor old one but I never reported it

  1. Have one or several packages open in Code Editor
  2. externally make something to one of them (for instance compile one of then in the DB Explorer)
  3. close the Code Editor …it will ask you if you want to reload the changed object = Unnecessary question …it should only close the editor (if you say yes it will reload and then close it :-))

Regards
Filipe


#2

I just can’t seem to reproduce. Did you close the code editor window or just a tab that contains the package?

Gwen


#3

Code Editor Window
I compiled one package that was used by another that was also opened.


#4

I can’t reproduce at all. After clicking on the close button, it just closes without prompting anything. It only prompt to reload if i switch between tabs.


#5

Hi Gwen

with the last buid I also am not able to reproduce the issue.

Regards
Filipe


#6

Thats good news Filipe. However, we didn’t fix anything related to this so we will have to keep an eye on this. Thanks a lot.

Gwen

Message was edited by: Gwen


#7

Hi again

here is how to get the message
0) in a schema with Team coding activated

  1. open a package (doing the check out)
  2. execute in another tab a create or replace script for that package
  3. close the editor

it can ask you to save to script: click no to all
it will ask you to for reloading the object

I hope you can reproduce this
Thanks
Filipe


#8

Hi Filipe,

No luck yet. We could not reproduce it here using the steps you provided :-).

Thanks,
Bruce


#9

Hi,

I have a similar Case here :

  • Open Package with Spec
  • Just Compile Body
  • Switch to Spec
  • Compile again
    Switch back to Body-Tab --> Same Message : “Current Database Object has been…”

SQL Navigator Beta Build 6.2.0.1498 / Expert Edition

Thanks, Ulrich


#10

Hi Ulrich,

Your case is actually as expected. When the package Spec is compiled, it also compiles the package body. When you switch tabs, sqlnav compares the current timestamp with the one in the DB and decides if the object has been changed. As a result, it will prompt the customer to reload.

In Filipe’s case, because he was closing the package, it should not check the timestamp and prompt him to reload. I could not reproduce the issue with the provided steps though.

Gwen


#11

OK, thank you Gwen

Ulrich


#12

um, Ok, SQL Nav needs to be smarter than that. If you compile the spec, in the same editor, asking if you want to reload the body is just stupid. Nav isn’t a stupid product which is why we love it. This is an annoyance, even if it isn’t a bug.

Personal opinion, this needs to be fixed. In actuality, it seems that when I have lots of packages open that are inter-related, this message happens a lot. It’s confusing and concerning and it may cause you to lose changes because it will reload when you haven’t saved changes in a related package.

I’ll see if I can duplicate the more complicated case, but this simple case, easily duplicated, should be fixed IMHO.

Jet


#13

Hi All,

We will look into it for you again in the area of this prompt in the product, and we will try to get the changes to you in a future Beta build.

Thanks and regards,
Bruce