Code insight seems to be broken in this version. List of objects is not being displayed.
I tried a few tests against an object I own, an object owned by another schema, and with the variables/tokens options on and off and in all cases objects were shown for me. Can you provide an example?
On 03/03/2015 10:40 AM, fisher_359 wrote:
Thread created by fisher_359
Code insight seems to be broken in this version. List of objects is not being displayed.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
I tried it in the same instance of Toad, in new tab, new editor window, on different connection as well. Finally Toad hanged while accepting parameters for sql. and crashed.
New Instance of Toad instance was free from issues I described before,
Unfortunately I cannot get any crash report from it.
Ok. I won’t spend too much on this right now because I intend to have a few Code Insight issues resolved for first beta of next week. 12.5 introduced the ability
to cancel fetching of objects. This works, but the infrastructure wasn’t properly set up for this asynchronous mode of operation. Performance problems are prominent with larger schemas and databases. I’ve been working on this for a few days and performance
timings are nearly identical to Toad 12.1 and the ability to cancel is retained. Let’s revisit your issue after I publish these updates.
In the meantime enable SQL Spooling and try to launch it. Are any queries being executed? If so try changing a few options to see if you can get it to work. I’d
disable both expected tokens and available identifiers first. If that doesn’t do it then disable Code Insight caching if it’s checked.
Thanks,
Michael
From: fisher_359 [mailto:bounce-fisher_359@toadworld.com]
Sent: Wednesday, March 04, 2015 1:21 AM
To: toadoraclebeta@toadworld.com
Subject: RE: [Toad for Oracle - Beta Discussion Forum] Toad (Code) Insight issues (12.7.0.49) 64 bit
RE: Toad (Code) Insight issues (12.7.0.49) 64 bit
Reply by fisher_359
I tried it in the same instance of Toad, in new tab, new editor window, on different connection as well. Finally Toad hanged while accepting parameters for sql. and crashed.
New Instance of Toad instance was free from issues I described before,
Unfortunately I cannot get any crash report from it.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.
Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
Michael,
I managed to recreate an issue in "freshly" open instance of Toad.
Paste following code in empty editor (line with mv_mailboxes was in line no 1 starts at co 5 )
select * from mv_mailboxes
trd_amu_rcpt_stats
cj
select * from mv_operators o where o.
select * from operators o where o.
List of columns from table operators is displayed only when I comment 1st line with sql on mv_mailboxes
or
if I end "select * from mv_operators o where o." with semicolon.
Maybe some issue with recognizing EOL as sql separator or combination of different issues.
mv* are materialized views - I only copied scripts for their tables.
trd_amu_rcpt_stats - is yet another table in my schema
Regards
Chris
On 2015-03-04 15:19, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by
Michael StaszewskiOk. I won't spend too much on this right now because I intend to have
a few Code Insight issues resolved for first beta of next week. 12.5
introduced the ability to cancel fetching of objects. This works, but
the infrastructure wasn't properly set up for this asynchronous mode
of operation. Performance problems are prominent with larger schemas
and databases. I've been working on this for a few days and
performance timings are nearly identical to Toad 12.1 and the ability
to cancel is retained. Let's revisit your issue after I publish these
updates.In the meantime enable SQL Spooling and try to launch it. Are any
queries being executed? If so try changing a few options to see if > you
can get it to work. I'd disable both expected tokens and available
identifiers first. If that doesn't do it then disable Code Insight
caching if it's checked.Thanks,
MichaelFROM: fisher_359 [mailto:bounce-fisher_359@toadworld.com]
SENT: Wednesday, March 04, 2015 1:21 AM
TO: toadoraclebeta@toadworld.com
SUBJECT: RE: [Toad for Oracle - Beta Discussion Forum] Toad (Code)
Insight issues (12.7.0.49) 64 bitRE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2]
Reply by fisher_359I tried it in the same instance of Toad, in new tab, new editor
window, on different connection as well. Finally Toad hanged while
accepting parameters for sql. and crashed.New Instance of Toad instance was free from issues I described > before,
Unfortunately I cannot get any crash report from it.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications > altogether.
Toad for Oracle - Beta Discussion ForumFlag [5] this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications > altogether.
Toad for Oracle - Beta Discussion ForumFlag [6] this post as spam/abuse.
Links:
More features are being converted to utilize the parser including Code Insight. I've mentioned this dozens of times in the past 10 years that properly terminating statements is important. I understand that many moons ago you could put any text in the Editor
and using CTRL+Enter you were safe to execute your statement provided you had no newlines. We've had an awesome parser for so many years now and much is gained by using it to its full potential.
Your text is syntactically incorrect in so many ways. The parser can't make sense of it. When you comment out the first line the parser gets closer, but it's still not correct. The text as you have it is interpreted as a single SELECT statement. When you comment
out the first line the parser interprets your text as 4 statements, the final one being a SELECT having the following text.
text: {
select * from mv_operators o where o.
select * from operators o where o.
}
line 7, column 1, offset 61, size 75
chunktype: {Select
}
name: {}
terminator: {} line 9, column 35, offset 136, size 0
Is it actually working for you? Do mv_operators and operators have the same list of columns? Double check that the root object is operators and not mv_operators. When I modify your code for objects I have here's what I see. Notices it's pulling from EMP, not
DEPT.
I'd start properly terminating statements. It's unreasonable to expect any IDE to be able to interpret gibberish as correct code. There are rules of syntax and when not followed it's kind of difficult to know what's going in.
Michael
On 03/05/2015 09:47 AM, fisher_359 wrote:
Reply by fisher_359
Michael,I managed to recreate an issue in "freshly" open instance of Toad.
Paste following code in empty editor (line with mv_mailboxes was in
line no 1 starts at co 5 )
select * from mv_mailboxes
trd_amu_rcpt_stats
cj
select * from mv_operators o where o.
select * from operators o where o.
List of columns from table operators is displayed only when I comment
1st line with sql on mv_mailboxes
or
if I end "select * from mv_operators o where o." with semicolon.
Maybe some issue with recognizing EOL as sql separator or combination
of different issues.
mv* are materialized views - I only copied scripts for their tables.
trd_amu_rcpt_stats - is yet another table in my schema
Regards
Chris
On 2015-03-04 15:19, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by
Michael Staszewski
Ok. I won't spend too much on this right now because I intend to have
a few Code Insight issues resolved for first beta of next week. 12.5
introduced the ability to cancel fetching of objects. This works, but
the infrastructure wasn't properly set up for this asynchronous mode
of operation. Performance problems are prominent with larger schemas
and databases. I've been working on this for a few days and
performance timings are nearly identical to Toad 12.1 and the ability
to cancel is retained. Let's revisit your issue after I publish these
updates.
In the meantime enable SQL Spooling and try to launch it. Are any
queries being executed? If so try changing a few options to see if
you
can get it to work. I'd disable both expected tokens and available
identifiers first. If that doesn't do it then disable Code Insight
caching if it's checked.
Thanks,
Michael
FROM: fisher_359 [mailto:bounce-fisher_359@toadworld.com]
SENT: Wednesday, March 04, 2015 1:21 AM
SUBJECT: RE: [Toad for Oracle - Beta Discussion Forum] Toad (Code)
Insight issues (12.7.0.49) 64 bit
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2]
Reply by fisher_359
I tried it in the same instance of Toad, in new tab, new editor
window, on different connection as well. Finally Toad hanged while
accepting parameters for sql. and crashed.
New Instance of Toad instance was free from issues I described
before,
Unfortunately I cannot get any crash report from it.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion Forum
Flag [5] this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion Forum
Flag this post as spam/abuse.
Links:
Michael,
It seems to me like getting back to discussion about considering EOL as SQL terminator, which I believe was to be implemented.
Reason why you see :
select * from mv_operators o where o.
select * from operators o where o.
is strictly because first one failed to display list of columns (Code Insight)
so I wanted to check if it's matter of aliases or anything else.
cj was another attempt of checking code templates if it still works as expected.
Honestly I still ain't understand why EOL as sql separator is considered such a bad thing?
Once this is in place (like it was for years) there'd be no problem with parsing this content.
From my point of view - your parser is failing with not recognizing EOL as sql terminator.
Chris
On 2015-03-05 16:12, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2] Reply by
Michael Staszewski
More features are being converted to utilize the parser including
Code Insight. I've mentioned this dozens of times in the past 10 > years
that properly terminating statements is important. I understand that
many moons ago you could put any text in the Editor and using
CTRL+Enter you were safe to execute your statement provided you had > no
newlines. We've had an awesome parser for so many years now and much
is gained by using it to its full potential.Your text is syntactically incorrect in so many ways. The parser
can't make sense of it. When you comment out the first line the > parser
gets closer, but it's still not correct. The text as you have it is
interpreted as a single SELECT statement. When you comment out the
first line the parser interprets your text as 4 statements, the final
one being a SELECT having the following text.text: {select * from mv_operators o where o.
select * from operators o where o.}
line 7, column 1, offset 61, size 75
chunktype: {Select}
name: {}
terminator: {} line 9, column 35, offset 136, size 0
Is it actually working for you? Do mv_operators and operators have
the same list of columns? Double check that the root object is
operators and not mv_operators. When I modify your code for objects I
have here's what I see. Notices it's pulling from EMP, not DEPT.I'd start properly terminating statements. It's unreasonable to
expect any IDE to be able to interpret gibberish as correct code.
There are rules of syntax and when not followed it's kind of > difficult
to know what's going in.Michael
On 03/05/2015 09:47 AM, fisher_359 wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by >> fisher_359
Michael,I managed to recreate an issue in "freshly" open instance of Toad.
Paste following code in empty editor (line with mv_mailboxes was in
line no 1 starts at co 5 )select * from mv_mailboxes
trd_amu_rcpt_stats
cj
select * from mv_operators o where o.
select * from operators o where o.
List of columns from table operators is displayed only when I >> comment
1st line with sql on mv_mailboxes
or
if I end "select * from mv_operators o where o." with semicolon.Maybe some issue with recognizing EOL as sql separator or >> combination
of different issues.mv* are materialized views - I only copied scripts for their tables.
trd_amu_rcpt_stats - is yet another table in my schemaRegards
ChrisOn 2015-03-04 15:19, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by
Michael StaszewskiOk. I won't spend too much on this right now because I intend to >> have
a few Code Insight issues resolved for first beta of next week. >> 12.5
introduced the ability to cancel fetching of objects. This works, >> but
the infrastructure wasn't properly set up for this asynchronous >> mode
of operation. Performance problems are prominent with larger >> schemas
and databases. I've been working on this for a few days and
performance timings are nearly identical to Toad 12.1 and the >> ability
to cancel is retained. Let's revisit your issue after I publish >> these
updates.In the meantime enable SQL Spooling and try to launch it. Are any
queries being executed? If so try changing a few options to see if
you
can get it to work. I'd disable both expected tokens and available
identifiers first. If that doesn't do it then disable Code Insight
caching if it's checked.Thanks,
MichaelFROM: fisher_359 [mailto:bounce-fisher_359@toadworld.com]
SENT: Wednesday, March 04, 2015 1:21 AM
TO: toadoraclebeta@toadworld.com
SUBJECT: RE: [Toad for Oracle - Beta Discussion Forum] Toad (Code)
Insight issues (12.7.0.49) 64 bitRE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2]
Reply by fisher_359I tried it in the same instance of Toad, in new tab, new editor
window, on different connection as well. Finally Toad hanged while
accepting parameters for sql. and crashed.New Instance of Toad instance was free from issues I described
before,Unfortunately I cannot get any crash report from it.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion ForumFlag [5] this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion ForumFlag this post as spam/abuse.
Links:
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications > altogether.
Toad for Oracle - Beta Discussion ForumFlag [5] this post as spam/abuse.
Links:
I believe was to be implemented.
It's in the works, but I'm not sure it will be completed in time for 12.7. The parser team is actively pursuing it.
Honestly I still ain't understand why EOL as sql separator is considered such a bad thing?
Toad sends code to Oracle and tries to follow the rules that Oracle has laid out for writing code. From what I've seen Oracle doesn't allow EOL separator. There's a SQLBLANKLINES setting, but that also requires a terminator.
Once this is in place (like it was for years) there'd be no problem with parsing this content.
It was that way in the beginning because there was no parser, blank lines were all that Toad had to go on. Once there was a parser features have slowly been converted to use it. Let's keep expectations realistic and view blank line terminator support in the
parser for what it is, a hack. With this support I suspect that having statements properly terminated on subsequent lines will not parse as multiple statements. Once we get the implementation from the parser team we can play with it and tweak it as needed,
but it's probably going to be either blank line terminator or ';' terminator, but not either or. I don't know for certain yet.
From my point of view - your parser is failing with not recognizing EOL as sql terminator.
EOL is not a terminator, but you're entitled to your opinion. SQL*Plus allows for
changing the terminator, but not to whitespace. You may want to take this up with Oracle.
Michael
On 03/05/2015 10:34 AM, fisher_359 wrote:
Reply by fisher_359
Michael,It seems to me like getting back to discussion about considering EOL as
SQL terminator, which I believe was to be implemented.
Reason why you see :
select * from mv_operators o where o.
select * from operators o where o.
is strictly because first one failed to display list of columns (Code
Insight)
so I wanted to check if it's matter of aliases or anything else.
cj was another attempt of checking code templates if it still works as
expected.
Honestly I still ain't understand why EOL as sql separator is
considered such a bad thing?
Once this is in place (like it was for years) there'd be no problem
with parsing this content.
From my point of view - your parser is failing with not recognizing EOL
as sql terminator.
Chris
On 2015-03-05 16:12, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2] Reply by
Michael Staszewski
More features are being converted to utilize the parser including
Code Insight. I've mentioned this dozens of times in the past 10
years
that properly terminating statements is important. I understand that
many moons ago you could put any text in the Editor and using
CTRL+Enter you were safe to execute your statement provided you had
no
newlines. We've had an awesome parser for so many years now and much
is gained by using it to its full potential.
Your text is syntactically incorrect in so many ways. The parser
can't make sense of it. When you comment out the first line the
parser
gets closer, but it's still not correct. The text as you have it is
interpreted as a single SELECT statement. When you comment out the
first line the parser interprets your text as 4 statements, the final
one being a SELECT having the following text.
text: {select * from mv_operators o where o.
select * from operators o where o.}
line 7, column 1, offset 61, size 75
chunktype: {Select}
name: {}
terminator: {} line 9, column 35, offset 136, size 0
Is it actually working for you? Do mv_operators and operators have
the same list of columns? Double check that the root object is
operators and not mv_operators. When I modify your code for objects I
have here's what I see. Notices it's pulling from EMP, not DEPT.
I'd start properly terminating statements. It's unreasonable to
expect any IDE to be able to interpret gibberish as correct code.
There are rules of syntax and when not followed it's kind of
difficult
to know what's going in.
Michael
On 03/05/2015 09:47 AM, fisher_359 wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by
fisher_359
Michael,
I managed to recreate an issue in "freshly" open instance of Toad.
Paste following code in empty editor (line with mv_mailboxes was in
line no 1 starts at co 5 )
select * from mv_mailboxes
trd_amu_rcpt_stats
cj
select * from mv_operators o where o.
select * from operators o where o.
List of columns from table operators is displayed only when I
comment
1st line with sql on mv_mailboxes
or
if I end "select * from mv_operators o where o." with semicolon.
Maybe some issue with recognizing EOL as sql separator or
combination
of different issues.
mv* are materialized views - I only copied scripts for their tables.
trd_amu_rcpt_stats - is yet another table in my schema
Regards
Chris
On 2015-03-04 15:19, Michael Staszewski wrote:
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [1] Reply by
Michael Staszewski
Ok. I won't spend too much on this right now because I intend to
have
a few Code Insight issues resolved for first beta of next week.
12.5
introduced the ability to cancel fetching of objects. This works,
but
the infrastructure wasn't properly set up for this asynchronous
mode
of operation. Performance problems are prominent with larger
schemas
and databases. I've been working on this for a few days and
performance timings are nearly identical to Toad 12.1 and the
ability
to cancel is retained. Let's revisit your issue after I publish
these
updates.
In the meantime enable SQL Spooling and try to launch it. Are any
queries being executed? If so try changing a few options to see if
you
can get it to work. I'd disable both expected tokens and available
identifiers first. If that doesn't do it then disable Code Insight
caching if it's checked.
Thanks,
Michael
FROM: fisher_359 [mailto:bounce-fisher_359@toadworld.com]
SENT: Wednesday, March 04, 2015 1:21 AM
SUBJECT: RE: [Toad for Oracle - Beta Discussion Forum] Toad (Code)
Insight issues (12.7.0.49) 64 bit
RE: TOAD (CODE) INSIGHT ISSUES (12.7.0.49) 64 BIT [2]
Reply by fisher_359
I tried it in the same instance of Toad, in new tab, new editor
window, on different connection as well. Finally Toad hanged while
accepting parameters for sql. and crashed.
New Instance of Toad instance was free from issues I described
before,
Unfortunately I cannot get any crash report from it.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion Forum
Flag [5] this post as spam/abuse.
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion Forum
Flag this post as spam/abuse.
Links:
To reply, please reply-all to this email.
Stop receiving emails [3] on this subject.
Or Unsubscribe from Toad for Oracle - Beta [4] notifications
altogether.
Toad for Oracle - Beta Discussion Forum
Flag [5] this post as spam/abuse.
Links:
Blank line terminator support has been added for next beta. There’s an option to enable it on the Execute/Compile options page. The option is disabled by default.
Michael,
Did it go in Beta Released (12.9.0.17) ?
I cannot see anything new in Execute/Compile, searching options for “blank” gives no results either
I sent you and email yesterday to your personal address, but we pulled it last minute because of a problem with multi-line statements. It will be in soon once we have the issue resolved.
Michael
On Jan 19, 2016, at 6:22 AM, fisher_359 bounce-fisher_359@toadworld.com wrote:
Reply by fisher_359
Michael,
Did it go in Beta Released (12.9.0.17) ?
I cannot see anything new in Execute/Compile, searching options for "blank" gives no results either
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.Toad for Oracle - Beta Discussion Forum
Flag
this post as spam/abuse.
is this still an issue in 12.8.0.49? Toad Insight is not appearing for me, despite many changes in the code assist form.
Does your situation follow that of the op where you have incomplete or erroneous code upstream of where you’re working? If so, yes 12.8 requires that your code is largely syntactically sound. The 12.9 beta has a new option in place that is more forgiving. If your code is syntactically sound and you’re not seeing the picklist then post a sample and/or screenshots that show the issue.
Michael