Menu

#1189 squirrel retains old query after disconnect

All
closed-fixed
nobody
None
5
2018-12-22
2015-03-10
Steve
No

Not sure what triggers this potential bug and it is not consistent in occurrence. When I have executed a query successfully, then stepped away and later executed another completely different query. The results from the first query are displayed rather than results for the new query. I try to reset using "Reconnect", but re-running the query still displays results from the previous SQL statement. The queries are not complex statements.

Example:
Query 1: Select * from pub.table_a
blah_a blah2_a blah3_a ....

Walk away for 15 minutes...

Query 2: Select * from pub.table_b
Expecting blah_b blah2_b blah3_b blah4_b ....
Instead I get blah_a blah2_a blah3_a .... from pub.table_a

Closing SQuirreL and restarting is a good workaround, but thought I would pass along this possible bug.

Details:
SQuirreL client v3.6
Connecting to a Progress Open Edge 11.3 database via ODBC Open Edge 11.3 driver
Windows Server 2012 R2.

Otherwise, I really enjoy working with this SQL client. I switched about 3 months ago from WinSQL.

Let me know if you need further info.

Steve

Discussion

  • Steve

    Steve - 2015-03-11

    This happened again to me today. It looks like it is happening because the query is returning 0 results due to a record-locking issue on the server side. The ODBC error is displayed in the SQuirreL message pane. Was not using a READ_UNCOMMITTED.

    java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Failure getting record lock on a record from table PUB.table_xyz.

    Somewhat misleading that my old query results are still displayed in SQuirreL.

    Steve

     
  • sfst

    sfst - 2018-11-16

    When I encountered this in the distant past it always turned out that I failed noticing that the new SQL command didn't actually deliver any output (there was an error message in the narrow bottom window) and I was staring at the output of the previous command. The Info tab with the execution date/time helps verifying the "age" of the output.

    That the old query result still is displayed is what I like from this product so much.

    Nowadays the error tab is a big improvement preventing this misunderstanding, so we can close this as solved?

     
  • Gerd Wagner

    Gerd Wagner - 2018-12-22
    • status: open --> closed-fixed
     
  • Gerd Wagner

    Gerd Wagner - 2018-12-22

    Closed as requested.
    Thanks.

     

Log in to post a comment.

MongoDB Logo MongoDB