This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Could this behaviour please be turned off or at least changed so that the insert cursor only moves if the cursor is not in the offending query within a file containing multiple queries. This can be frustrating in a number of scenarios. - The cursor was already at the offending place within the query. - The query is executed, then the editor changes are being made while a long running query is executing, the cursor changes position while still typing after the execution completes. One option would be to make the cursor move smarter, but this would involve managing the error output from various drivers and I don't think this is feasible. Optionally have a configurable option to turn this behaviour off, but; don't move the cursor if we're already in the same query.
Your argumentation is sound - the change was introduced together with the fix for #189051. The system tries to extract the correct location of an error, but relies on a supported DBMS to do this. So the error location is still reported now, but the caret is not moved anymore. The fix is pushed as: http://hg.netbeans.org/core-main/rev/7fdd3974b83e
Integrated into 'main-silver', will be available in build *201701120001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/7fdd3974b83e User: Matthias Blaesing <matthias42@netbeans.org> Log: #268794: Revert automatic caret movement introduced with fix for #189051 The intention of the implementation was to make it easier to react to errors, but in bug report #268794 valid points were raised, that made this impractical: - The cursor was already at the offending place within the query. - The query is executed, then the editor changes are being made while a long running query is executing, the cursor changes position while still typing after the execution completes. As not all DBMS return valid or precise locations, this part of the fix is reverted.
*** Bug 270530 has been marked as a duplicate of this bug. ***