In .41, type three valid SELECT SQLs in the Editor:
select * from dual;
select * from dual;
select * from dual;
Move back up to the second one and type – don’t paste – an Oracle hint ("/*+ parallel */") just after the SELECT. While typing (unless you’re freakishly faster than me), a bang appears in the margin after the third SELECT. But after completing the comment/hint, the bang doesn’t go away. The “s” in the first “select” is also underscored, looking like it’s invalid. Cut and re-paste the entire buffer and the bang goes away.
I’ve hit this a bunch, but wasn’t able to duplicate it until now…phew!
TIA!
Rich
Disclaimer: I claim no responsibility for the “eggnog” tag in the “Select Tags” for forum posts.
Before I hack around this one I sent it to the parser team. There is one known issue already (and now this one) where error messages returned include incorrect location information. It looks like the parser results we have are still accurate so executing will
still execute the correct statement even though the indication of error is wrong. I'll await their response before addressing it.
In .41, type three valid SELECT SQLs in the Editor:
select * from dual;
select * from dual;
select * from dual;
Move back up to the second one and type -- don't paste -- an Oracle hint ("/*+ parallel */") just after the SELECT. While typing (unless you're freakishly faster than me), a bang appears in the margin after the first SELECT. But after completing
the comment/hint, the bang doesn't go away. The "s" in the first "select" is also underscored, looking like it's invalid. Cut and re-paste the entire buffer and the bang goes away.
I've hit this a bunch, but wasn't able to duplicate it until now...phew!
TIA!
Rich
Disclaimer: I claim no responsibility for the "eggnog" tag in the "Select Tags" for forum posts.
