Res, ql = query.execute_with_logging(user)įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\models.py", line 87, in execute_with_loggingįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\models.py", line 93, in executeįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\models.py", line 81, in execute_query_onlyįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\models.py", line 194, in init Return super().dispatch(request, *args, **kwargs)įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\django\views\generic\base.py", line 98, in dispatchįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\views\query.py", line 97, in getįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\views\utils.py", line 19, in query_viewmodel Return self.dispatch(request, *args, **kwargs)įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\explorer\views\auth.py", line 44, in dispatch Response = wrapped_callback(request, *callback_args, **callback_kwargs)įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\django\views\generic\base.py", line 70, in view The above exception (('HY010', ' Function sequence error (0) (SQLFetch)')) was the direct cause of the following exception:įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\django\core\handlers\exception.py", line 47, in innerįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\django\core\handlers\base.py", line 179, in _get_response '']įile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\django\db\utils.py", line 97, in innerįile "\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\sql_server\pyodbc\base.py", line 601, in fetchall '\\FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages'] 'c:\users\myxaccnt\appdata\local\programs\python\python38-32', '\\FSE0238\myxhome$\Projects\GEAR\Django\env\Scripts\python38.zip',
Python Executable: \FSE0238\myxhome$\Projects\GEAR\Django\env\Scripts\python.exe ('HY010', ' Function sequence error (0) (SQLFetch)')Įxception Value: ('HY010', ' Function sequence error (0) (SQLFetch)')Įxception Location: \FSE0238\myxhome$\Projects\GEAR\Django\env\lib\site-packages\sql_server\pyodbc\base.py, line 601, in fetchall
Note that v2.0b does fix "virtual foldering" issues in the home page query list, which was the main reason to upgrade. (Adding the AutoCommit = False option in Settings does not change anything Researching the issue shows that common causes include issuing a Commit after a Select, and order of operations regarding cursors, including async operations too quickly. Can navigate to the Playground page and view the schema, but even the simplest query produces the same error.ĭjango and other components are current, and also tried updating to ODBC Driver 17, and getting the same results. The SQL Explorer home page updates properly, adding/updating items to the Most Recently Run list with the right date, even though the query did not actually run. 'HY010', ' Function sequence error (0) (SQLFetch)'Īll queries are on the same table in SQL Server 2014 and worked without issue in v1.1.3. I just upgraded SQL Explorer from v1.1.3 to v2.0b and now all queries produce the same runtime error when opened:
0 kommentar(er)
