database

Documentation

Index

• func Asset(name string) ([]byte, error)
• func AssetDir(name string) ([]string, error)
• func AssetInfo(name string) (os.FileInfo, error)
• func AssetNames() []string
• func MustAsset(name string) []byte
• func RestoreAsset(dir, name string) error
• func RestoreAssets(dir, name string) error
• type Client
• type Clients
• type ConflictAction
• type DBServer
  • func NewDBServer(conf *config.DB, log *log.Logger) (*DBServer, error)
  • func (s *DBServer) Close() error
  • func (s *DBServer) CreateClient(clientId string, name string) (*Client, error)
  • func (s *DBServer) DeleteClient(id int) (interface{}, error)
  • func (s *DBServer) GetAllClients() (*Clients, error)
  • func (s *DBServer) GetClient(id int) (*Client, error)
  • func (s *DBServer) QueryRow(id string) *pgx.Row
  • func (s *DBServer) UpdateClient(id string, name string, status string) (interface{}, error)

Functions

func Asset

func Asset(name string) ([]byte, error)

Asset loads and returns the asset for the given name. It returns an error if the asset could not be found or could not be loaded.

func AssetDir

func AssetDir(name string) ([]string, error)

AssetDir returns the file names below a certain directory embedded in the file by go-bindata. For example if you run go-bindata on data/... and data contains the following hierarchy:

data/
  foo.txt
  img/
    a.png
    b.png

then AssetDir("data") would return []string{"foo.txt", "img"} AssetDir("data/img") would return []string{"a.png", "b.png"} AssetDir("foo.txt") and AssetDir("notexist") would return an error AssetDir("") will return []string{"data"}.

func AssetInfo

func AssetInfo(name string) (os.FileInfo, error)

AssetInfo loads and returns the asset info for the given name. It returns an error if the asset could not be found or could not be loaded.

func AssetNames

func AssetNames() []string

AssetNames returns the names of the assets.

func MustAsset

func MustAsset(name string) []byte

MustAsset is like Asset but panics when Asset would return an error. It simplifies safe initialization of global variables.

func RestoreAsset

func RestoreAsset(dir, name string) error

RestoreAsset restores an asset under the given directory

func RestoreAssets

func RestoreAssets(dir, name string) error

RestoreAssets restores an asset under the given directory recursively

Types

type Client

type Client struct {
	Id       int32   `json:"id"`
	ClientId *string `json:"clientId"`
	Name     *string `json:"name"`
}

type Clients

type Clients struct {
	Clients *[]Client `json:"clients"`
}

type ConflictAction

type ConflictAction int

ConflictAction is an enum used for BuildOnConflict

const (
	CAUnknown ConflictAction = iota
	CANothing
	CAUpdate
)

This is the closest thing to enums in go :(

type DBServer

type DBServer struct {
	Ready chan bool
	// contains filtered or unexported fields
}

DBServer contains the configuration, db connection pool and logging for the package

Why 'ready' channel? We run DB migrations in a goroutine because we can't block startup of the service (it times out). We need a way to know when DB migrations are done, so we send notification via the 'ready' channel.

func NewDBServer

func NewDBServer(conf *config.DB, log *log.Logger) (*DBServer, error)

NewDBServer returns a DB structs and also setups the DB and runs migrations

func (*DBServer) Close

func (s *DBServer) Close() error

Close disconnects from the database

func (*DBServer) CreateClient

func (s *DBServer) CreateClient(clientId string, name string) (*Client, error)

func (*DBServer) DeleteClient

func (s *DBServer) DeleteClient(id int) (interface{}, error)

func (*DBServer) GetAllClients

func (s *DBServer) GetAllClients() (*Clients, error)

func (*DBServer) GetClient

func (s *DBServer) GetClient(id int) (*Client, error)

func (*DBServer) QueryRow

func (s *DBServer) QueryRow(id string) *pgx.Row

Used for testing only

func (*DBServer) UpdateClient

func (s *DBServer) UpdateClient(id string, name string, status string) (interface{}, error)