Introduce model.Transaction()

It is a very common pattern that some function needs to access the
database and wants to wrap all the actions into one transaction.

The advantage of a transaction is that it is ACID:

- atomic
- consistent
- isolated
- durable

In Go it is required to request a new transaction, execute functionality
on it and handle rollback or commit of this transaction based on the
success of the operation.

All this and the error handling can be written down in the
model.Transaction() function exactly once. The full signature of it is:

	func Transaction(f func(*sql.Tx) error) error

It requires a function or closure passed as argument which takes the
transaction (*sql.Tx) and returns an error which might be nil.

This is very generic. It is applied to:

- injecting test data
- database migrations
- data read requests
- data write requests

1 files changed, 0 insertions, 15 deletions

diff --git a/model/object.go b/model/object.go
index bcbba3e..63ef419 100644
--- a/model/object.go
+++ b/model/object.go
@@ -10,18 +10,3 @@ type Object interface {
 	Update(tx *sql.Tx) error
 	Delete(tx *sql.Tx) error
 }
-
-func SafeCrud(crud func(tx *sql.Tx) error) error {
-	tx, err := NewTx()
-	if err != nil {
-		return err
-	}
-
-	err = crud(tx)
-	if err != nil {
-		Rollback(tx)
-		return err
-	}
-
-	return tx.Commit()
-}