Closed ajoses closed 3 years ago
Sorry I don't have any knowledge. I want somebody's help !
Hi,
I think I found the issue of the transaction open during the time of the connection. It's the first transaction after opening the transaction.
I did some test and I modify the following:
All this changes is because the transaction open for long time and of type Read/Write affect the performance of the database, even reach the point to the need of the sweeper wich kills the database perfomance.
I think the changes improves a little the transaction management, that is something very important in Firebird.
Anything please inform me.
Pull Request #91
Thanks!
Pull Request #91 seems good, so I have merged it.
But...
$ go test
--- FAIL: TestIssue89 (1.13s)
transaction_test.go:387: Autocommit in prepare don't work
FAIL
exit status 1
FAIL _/home/nakagami/firebirdsql 34.124s
I will investigate in detail later
fix test
Hi,
I'm having an Issue with the commit of transaction.
Normally with Firebird I use one connection object and then I use multiple transactions to do the querys. However in golang with this driver it leaves the transaction open, so after a while of using my program there are a lot of transactions. From the perspective of Firebird is bad because after a while it decrease the performance.
My code for open the connection is the following:
The variable Conexion is a global variable that I use in all the program, then when I need to do a query I do the following:
Normally with each function I start in the same way if the function will be using something of the DB, I started to see the problem when inside a function I call another function that has the same structure.
I don't know if it's something of Go, any idea will be helpful.
Greetings Arnulfo José