Transactions can't be managed explicitly

[awhalbert]

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
  • 
• ADS PostgresSQL etension version
  • v0.4.2
• PostgreSQL version
  • PostgreSQL 12.7, compiled by Visual C++ build 1914, 64-bit

[mistermiracl]

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

[S4NT14G0]

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

[DaeunYim]

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]

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]

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

[DaeunYim]

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

[nasc17]

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

[awhalbert]

Yes, looks good now, thanks!