field-codecs

Field transformation transparently encrypts struct fields during database interactions without altering the Go type. You register a custom codec and tag the field, ensuring type safety while encoding and decoding sensitive data on the fly.

Yes, transparent JSON or GOB serialization is supported using built-in codecs. By registering the appropriate codec and tagging your struct field, data is automatically serialized when stored and deserialized when read, maintaining your original Go type.

Codec registration involves defining a custom codec function and registering it with a specific tag name. You then apply this tag to your struct fields, enabling the automatic encoding and decoding of values during database reads and writes without manual wrapping.

Using a built-in Unix Time codec is the best way to handle Unix timestamp conversion. It automatically transforms your time fields to and from Unix timestamps in the database, maintaining type safety and efficiency without altering your Go struct's time type.

No, this approach maintains type safety and eliminates the need to wrap every read or write operation. It transparently transforms values using registered codecs based on struct tags, keeping your original Go types clean and efficient.

You need a custom codec for database field encryption when utilizing specific encryption algorithms not covered by built-in options. Defining and registering a custom codec function allows you to apply specialized encryption logic to your struct fields transparently.