Sqlx: Generic *sqlx.DB or *sqlx.Tx?

[mewben]

Hi, is there a way I could accept a parameter which is either sqlx.DB or sqlx.Tx?

I have this function wherein I have to pass *sqlx.DB:

func GetUser(db *sqlx.DB, username string) ...

There's no problem with this, until I create a new Transaction and inside that transaction, I need to call GetUser. So I ended up implementing 2 functions to provide the same result...

func GetUser2(tx *sqlx.Tx, username string) ...

Is there a way I can make this into 1 function? I tried this:

func GetUser(db *sqlx.DB, tx *sqlx.Tx, username string) (*User, error) {
  if tx != nil {
    // use tx
  } else {
    // use db
  }
  ...
}

but is this okay? I wish there is something like this:

func GetUser(db *sqlx.DBorTxSomething, ...

:)

[jhngrant]

@mewben This is consistent with *sql.Tx and *sql.DB in the standard library.

Over in golang-nuts, @davecheney suggests defining your own interface.

See: https://groups.google.com/forum/#!topic/golang-nuts/yLg6IWbwPPw

[alhails]

@mewben I've achieved this by creating an interface that covers the sqlx methods I need and then creating two implementations that wrap sqlx.DB and sqlx.Tx respectively. Then your GetUser method can accept that interface instead of the concrete types.

[eexit]

Hey, you need to create a common interface that is used by both *sqlx.DB and *sqlx.Tx.
Example:

type DB interface {
    Querier
    Begin() (Tx, error)
    Close() error
}

type Tx interface {
    Querier
    Commit() error
    Rollback() error
}

type Querier interface {
    QueryRow(query string, args ...interface{}) Row
    Select(dest interface{}, query string, args ...interface{}) error
    NamedQuery(query string, arg interface{}) (Rows, error)
    NamedExec(query string, arg interface{}) (sql.Result, error)
}


func GetUser(q *Querier, username string) {}

But of course, it requires you to wrap sqlx :)

[mewben]

Ahhh.. I get it now.. Thank you all...

[tj]

I'd still love to see this, bit of a pain to need yet-another layer. It'd be easy to argue it's not sqlx's concern, but sqlx exists to provide convenience so it seems fine to me.