microsoft/azuredatastudio-postgresql

Transactions can't be managed explicitly

awhalbert opened this issue · 8 comments

awhalbert commented

Description
BEGIN;
INSERT INTO foo
VALUES ('foo');
ROLLBACK;

The above commits, rather than rolls back. The value exists in the table.

Repro
Try to use explicit transactions and control whether they commit or roll back.

OS
Windows 11 Enterprise Version 10.0.22621 Build 22621

Versions

  • ADS
    • image
  • ADS PostgresSQL etension version
    • v0.4.2
  • PostgreSQL version
    • PostgreSQL 12.7, compiled by Visual C++ build 1914, 64-bit
mistermiracl commented

I can confirm this, when I was on 0.2.7 I could use explicit transaction without any issues, now that I'm on 0.4.2 BEGIN/BEGIN TRANSACTION are simply ignored

  • 👍1
S4NT14G0 commented

Same issue here. Basically rendering this unusable for me and my team.

  • 😕1
DaeunYim commented

We will work on the fix. Meanwhile, you can download the previous version here https://github.com/microsoft/azuredatastudio-postgresql/releases/tag/v0.3.1

nasc17 commented

Hello, issue has been addressed in our unstable release of PostgreSQL extension v0.4.3-insiders. We would appreciate your verification that it has been handled appropriately.

awhalbert commented

Hi, I installed 0.4.3 (Win64) but I get this when I try to initiate any database connection:
image

DaeunYim commented

@awhalbert can you check the latest stable release 0.5.0? Otherwise, we will need more information on your connection params.

nasc17 commented

Bug has been addressed in latest stable release of PostgreSQL extension v0.5.0. Please reopen if issue is still present, thank you.

awhalbert commented

Yes, looks good now, thanks!

  • 👍2
  • ❤️2