using aliases hangs my toad session. Below is the example.
Select * from mytable a where a.(dot) When I type (.) in SQL Editor it hangs and never returns the cursor and I need to forcefully kill the toad session.
it will be really important if you could place toad version you are using as well as oracle client version.
Hi All,
Toad version 12.6 I.e. latest version. Oracle client version11gr2.
Best Regards,
Bilal
Sent from Samsung Mobile
-------- Original message -----
Hi,
in toad 12.7.06 beta x64, works correctly on similar query:
__select * from user_tables a where a. __
in toad 12.6.0.53 x64, works as well.
In mine cases, user_tables is know view with single reference to object.
I think you have confused Toad with private-public synonyms (or same named different objects).
Please query (F4 on your “mytable”) and look what will toad suggest you as result…
Hope this helps,
Damir
Is it just the alias? What is you just type mytable. and wait for the popup? Does it still hang? There's a known issue when using it with very large schemas. In particular the APPS schema with Oracle E-Business Suite has come up several times. It's on my todo
list for 12.7. Does the schema in question contain many objects?
On 10/26/2014 06:51 AM, bmohammed1 wrote:
Thread created by bmohammed1
using aliases hangs my toad session. Below is the example.
Select * from mytable a where a.(dot) When I type
(.) in SQL Editor it hangs and never returns the cursor and I need to forcefully kill the toad session.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
MIchael, there’s something very wrong going with TI in general:
-
it’s way slower on the same schema than previous versions.
-
Toad used to consider empty line as sql separator, now it requires semicolon to make TI working. It’s just not what I’m (and I believe some other users) used to.
it’s inconsistent also inconsistent, since Ctrl + H combination still uses empty line or semicolon.
That all makes me just using 12…0.1.2. I guess you should be more careful with changes in such a fragile area.
There are two known performance issues. The first is when connected to large schemas. The APPS schema in Oracle E-Business Suite has come up several times. The second is when invoking within large PL/SQL as reported by PaulZip. This one is fixed in the next
beta. Generally speaking it will be slower than in previous versions because of changes that were made to thread the queries executed; however, it should not be as slow as it is in the scenarios that have come through support and and the forums. I'll address
these in this release.
Back in the day an empty line separator was supported because that was all we had to go on. We had no parser. We now have an incredible parser that does much more than identify statements. It allows us to query the statement structure for the various clauses,
aliases, table references, etc. with speed and accuracy. To use it the code needs to be (mostly) syntactically correct, including proper termination of statements. Once more than 1 statement exists the rules of script writing must be followed. Empty line terminators,
CTRL+H, and CTRL+Enter|Shift+F9 are total hacks. The use of those should be avoided at all costs. The programming languages I use all require following rules of syntax. If I have an error upstream of where I'm working, features of the IDE fail to work properly.
This is nothing specific to Toad, it's how programming languages are structured and how parsers makes sense of the code. Going forward as new features are introduced and old features are reworked empty line terminator support will be dropped as it has been
here. If you want to throw together a query without terminating your statements you'll need to use a new tab containing only that query.
Michael
On 10/30/2014 08:22 AM, fisher_359 wrote:
Reply by fisher_359
MIchael, there's something very wrong going with TI in general:
- it's way slower on the same schema than previous versions.
- Toad used to consider empty line as sql separator, now it requires semicolon to make TI working. It's just not what I'm (and I believe some other users) used to.
it's inconsistent also inconsistent, since Ctrl + H combination still uses empty line or semicolon.
That all makes me just using 12..0.1.2. I guess you should be more careful with changes in such a fragile area.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
Hi All,
I face the situation when connected to apps schema. Is there a fix for this. I am currently on latest toad version.
Best Regards,
Bilal
Sent from Samsung Mobile
-------- Original message -----
The APPS issue is still outstanding. It will be fixed during the 12.7 release cycle.
On 10/30/2014 10:28 AM, bmohammed1 wrote:
Reply by bmohammed1
Hi All,I face the situation when connected to apps schema. Is there a fix for this. I am currently on latest toad version.
Best Regards,
Bilal
Sent from Samsung Mobile
Thanks Micheal for the information. Any tentative date for 12.7 release. And also any workaround for this issue.
Best Regards,
Bilal
Sent from Samsung Mobile
-------- Original message -----
12.7 is a spring release so it will be April(ish) most likely. Our beta cycle is active now and once it's fixed I'll post a message. If you can use the beta you'll have a several month jump on the official release. I don't know of any workarounds other than
limit the number of objects that Code Insight displays the the smallest set you can. I don't know if that will do too much for you, but it's worth a shot. I think that some users were having better success depending on how they were logged in and accessing
APPS, but I may be mistaken. You can try the following to see if one works better for you. 1. Log in directly as APPS. 2. Log in and set your current schema to APPS (use the dropdown on the Editor toolbar). 3. Log in as another schema and reference APPS. You're
doing one of those already so try the others if possible.
On 10/30/2014 10:42 AM, bmohammed1 wrote:
Reply by bmohammed1
Thanks Micheal for the information. Any tentative date for 12.7 release. And also any workaround for this issue.Best Regards,
Bilal
Sent from Samsung Mobile
That’s one scary message.
Ability to work with EOL sql separator, Ctrl+H and some other "as you called them “hacks” keeps me using Toad at all.
Since for example:
-
debugging is far from perfect,
-
ToadInside… let me put it this way if you’re made to use it for a month in IDE you use for your development - you’d have changed that thing,
-
Navigator in Editor - very close to debugger.
TI in recent releases is just not user friendly at all, on top of that is very slow (compared with connection to the same schema on the same DB) - I cannot figure out where do you see any benefits from now parser in it
If I’m not mistaken Ctrl-H was imposed by Quest, previously we could get explain plan of current sql without selecting it.
now it’s bringing features it down to what for example SQL developer does.
I’m not really sure how alternative sql terminator (EOL) is breaking breaking any rules of syntax?
" If I have an error upstream of where I’m working, features of the IDE fail to work properly"
and honestly would not you prefer Intellisense or navigator still work even though there’s some syntax issue (like not complete statement or undeclared variable few hundred lines above) ? I cannot believe you experience anything like this in Embarcadero or VS.
I use Toad since nearly it’s beginning I realize I’ve my own ways with it, things I got used to.
Well at the end I might stick to old version after all or move to some other tool.
Cancer scary or boogie man scary? It makes a big difference.
"if you're made to use it for a month in IDE you use for your development - you'd have changed that thing"
And it will be changed in this release cycle. These issues came to light post release via support. This is how the process works. We release, users report issues, we fix in the upcoming release. That's where we're at now. I can't go back in time and change that thing. If you're not a beta user, consider becoming one. You can report issues so that we can address them prior to the release.
"debugging is far from perfect"
We currently use Oracle's DBMS debugger. We work with what we have. It's not perfect. Specifically what are your problems? If you post specific problems we have something to go on and can investigate if it's a Toad issue or a limitation.
"If I'm not mistaken Ctrl-H was imposed by Quest, previously we could get explain plan of current sql without selecting it."
CTRL+H was a concession because users were having a hard time adjusting to properly terminating statements. It was made clear that proper termination would be a good practice to adopt.
"how alternative sql terminator (EOL) is breaking breaking any rules of syntax"
Oracle requires terminators, the default being semicolon. There is a SET SQLTERMINATOR property for SQL*Plus although I can't seem to set it to a newline and my Google searches have been fruitless. If you have success let me know and we can see about incorporating it.
"honestly would not you prefer Intellisense or navigator still work even though there's some syntax issue"
Of course, but I also understand that an algorithm is used following rules of syntax and if an error upstream prevents proper parsing then features may not work.
"I cannot believe you experience anything like this in Embarcadero or VS"
Review the first suggestion from MS when IntelliSense is not working. Delphi is pretty much the same. Sometimes it works, sometimes it does not. It all depends on the location and type of error and whether or not the IDE does any caching of previously known identifiers.
"I realize I've my own ways with it, things I got used to."
I'm sure this guy said the same thing once or twice.
On 11/03/2014 09:51 AM, fisher_359 wrote:
RE: using aliases hangs my toad session
Reply by fisher_359
That's one scary message.
Ability to work with EOL sql separator, Ctrl+H and some other "as you called them "hacks" keeps me using Toad at all.
Since for example:
- debugging is far from perfect,
- ToadInside.... let me put it this way if you're made to use it for a month in IDE you use for your development - you'd have changed that thing,
- Navigator in Editor - very close to debugger.
TI in recent releases is just not user friendly at all, on top of that is very slow (compared with connection to the same schema on the same DB) - I cannot figure out where do you see any benefits from now parser in it
If I'm not mistaken Ctrl-H was imposed by Quest, previously we could get explain plan of current sql without selecting it.
now it's bringing features it down to what for example SQL developer does.
I'm not really sure how alternative sql terminator (EOL) is breaking breaking any rules of syntax?
" If I have an error upstream of where I'm working, features of the IDE fail to work properly"
and honestly would not you prefer Intellisense or navigator still work even though there's some syntax issue (like not complete statement or undeclared variable few hundred lines above) ? I cannot believe you experience anything like this in Embarcadero or VS.
I use Toad since nearly it's beginning I realize I've my own ways with it, things I got used to.
Well at the end I might stick to old version after all or move to some other tool.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
Flag this post as spam/abuse.
We're investigating the possibility of having blank line terminator support natively in the parser. This would be an ideal solution because it allows for converting legacy code over to use the parser (better speed and accuracy) and still allows you to write
code as you've always done. It's not compatible with SQL*Plus or other tools, but if you're not using terminators now anyway I doubt that will be a problem. I'll keep you posted.
On the navigator, what specifically are your issues? Is it back to the newline terminator where you have what you perceive to be N statements, but Toad thinks otherwise and displays less statements, unknown, or other information that does not conform to your
code? If so, a blank line terminator option would address this as well as the explain plan selection hurdle.
On 11/03/2014 09:51 AM, fisher_359 wrote:
Reply by fisher_359
That's one scary message.
Ability to work with EOL sql separator, Ctrl+H and some other "as you called them "hacks" keeps me using Toad at all.
Since for example:
- debugging is far from perfect,
- ToadInside.... let me put it this way if you're made to use it for a month in IDE you use for your development - you'd have changed that thing,
- Navigator in Editor - very close to debugger.
TI in recent releases is just not user friendly at all, on top of that is very slow (compared with connection to the same schema on the same DB) - I cannot figure out where do you see any benefits from now parser in it
If I'm not mistaken Ctrl-H was imposed by Quest, previously we could get explain plan of current sql without selecting it.
now it's bringing features it down to what for example SQL developer does.
I'm not really sure how alternative sql terminator (EOL) is breaking breaking any rules of syntax?
" If I have an error upstream of where I'm working, features of the IDE fail to work properly"
and honestly would not you prefer Intellisense or navigator still work even though there's some syntax issue (like not complete statement or undeclared variable few hundred lines above) ? I cannot believe you experience anything like this in Embarcadero
or VS.
I use Toad since nearly it's beginning I realize I've my own ways with it, things I got used to.
Well at the end I might stick to old version after all or move to some other tool.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
The Code Insight performance problems listed in this thread are fixed for 12.7. The fix will be available in 12.7.0.52 beta. Please have a look and let me know if things are better. Performance should be on par with older versions in my testing.