No description
Find a file
2015-09-10 12:49:41 -04:00
zero fix govet warnings 2015-01-28 15:15:30 +09:00
.gitignore initial commit 2014-08-29 00:11:18 +09:00
bool.go improve godoc 2015-01-21 11:33:38 +09:00
bool_test.go fix govet warnings 2015-01-28 15:15:30 +09:00
float.go improve godoc 2015-01-21 11:33:38 +09:00
float_test.go fix govet warnings 2015-01-28 15:15:30 +09:00
int.go improve godoc 2015-01-21 11:33:38 +09:00
int_test.go fix govet warnings 2015-01-28 15:15:30 +09:00
LICENSE initial commit 2014-08-29 00:11:18 +09:00
README.md improve godoc 2015-01-21 11:33:38 +09:00
string.go improve godoc 2015-01-21 11:33:38 +09:00
string_test.go UnmarshalJSON returns an error for invalid zero.* types, tests 2014-09-09 12:31:58 +09:00
time.go Scanning nil for null.Time creates value with Valid = false rather than erroring 2015-09-10 12:49:41 -04:00
time_test.go Add null.Time and testing 2015-09-08 17:28:31 -04:00

null GoDoc Coverage

import "gopkg.in/guregu/null.v2"

null is a library with reasonable options for dealing with nullable SQL and JSON values

There are two packages: null and its subpackage zero.

Types in null will only be considered null on null input, and will JSON encode to null. If you need zero and null be considered separate values, use these.

Types in zero are treated like zero values in Go: blank string input will produce a null zero.String, and null Strings will JSON encode to "". If you need zero and null treated the same, use these.

All types implement sql.Scanner and driver.Valuer, so you can use this library in place of sql.NullXXX. All types also implement: encoding.TextMarshaler, encoding.TextUnmarshaler, json.Marshaler, and json.Unmarshaler.

zero.String

A nullable string.

Will marshal to a blank string if null. Blank string input produces a null String. In other words, null values and empty values are considered equivalent. Can unmarshal from sql.NullString JSON input.

zero.Int

A nullable int64.

Will marshal to 0 if null. Blank string or 0 input produces a null Int. In other words, null values and empty values are considered equivalent. Can unmarshal from sql.NullInt64 JSON input.

zero.Float

A nullable float64.

Will marshal to 0 if null. Blank string or 0 input produces a null Float. In other words, null values and empty values are considered equivalent. Can unmarshal from sql.NullFloat64 JSON input.

zero.Bool

A nullable bool.

Will marshal to false if null. Blank string or false input produces a null Float. In other words, null values and empty values are considered equivalent. Can unmarshal from sql.NullBool JSON input.

null.String

An even nuller nullable string.

Unlike zero.String, null.String will marshal to null if null. Zero (blank) input will not produce a null String. Can unmarshal from sql.NullString JSON input.

null.Int

An even nuller nullable int64.

Unlike zero.Int, null.Int will marshal to null if null. Zero input will not produce a null Int. Can unmarshal from sql.NullInt64 JSON input.

null.Float

An even nuller nullable float64.

Unlike zero.Float, null.Float will marshal to null if null. Zero input will not produce a null Float. Can unmarshal from sql.NullFloat64 JSON input.

null.Bool

An even nuller nullable float64.

Unlike zero.Bool, null.Bool will marshal to null if null. False input will not produce a null Bool. Can unmarshal from sql.NullBool JSON input.

Bugs

json's ",omitempty" struct tag does not work correctly right now. It will never omit a null or empty String. This should be fixed eventually.

License

BSD