Print

Print


On Jun 25, 2016 8:38 PM, "Young,Jeff (OR)" <[log in to unmask]> wrote:

> Exotic datatypes seem like a backwater solution.

It even creates it's own backwater...

Using a  custom datatype requires custom support and implementation. It
requires careful definition of the lexical and value spaces, and the
mapping from one to the other.

Using property hierarchies doesn't.

It's possible to implement a native datatype for PostgresSQL that can store
a MARC record in a single column. That's not always the best way to go.

Simon