Why use tx object for execute requests after call Rollback or Commit does not throw errors?

[stasvo]

I see that if call transaction rollback and after it use same tx object for execute requests, instead of get error
from execute operation, they will be executed without errors, and they will not need a commit, same as if use connection object without transaction.

tx, err := dbpool.Begin(context.Background())
if err != nil {
	return
}

err = tx.Rollback(context.Background())
if err != nil {
	return
}

user1 := model.User{Name: "Belka", Email: "[email protected]"}
_, err = tx.Exec(context.Background(), "insert into users (name, email, created_at) VALUES "+
	"($1, $2, now())", user1.Name, user1.Email)
if err != nil {
	log.Println(err)
	return
}

Also I see that if call transaction commit and after it use same tx object for execute requests, instead of get error
from execute operation, they will be executed without errors in same way as were used connection object without transaction.

tx, err := dbpool.Begin(context.Background())
if err != nil {
	return
}

user1 := model.User{Name: "Belka", Email: "[email protected]"}
_, err = tx.Exec(context.Background(), "insert into users (name, email, created_at) VALUES "+
	"($1, $2, now())", user1.Name, user1.Email)
if err != nil {
	log.Println(err)
	return
}

err = tx.Commit(context.Background())
if err != nil {
	log.Println("коммит", err)
	return
}

user2 := model.User{Name: "Strelka", Email: "[email protected]"}
_, err = tx.Exec(context.Background(), "insert into users (name, email, created_at) VALUES "+
	"($1, $2, now())", user2.Name, user2.Email)
if err != nil {
	log.Println(err)
	return
}

Why is it so? ?

[jackc]

Why is it so?

It was an oversight. The other methods have a guard clause:

	if tx.closed {
		return nil, ErrTxClosed
	}

But apparently I missed it for Exec. Fixed in 3ad9995.