SQLPrimitive

The innocent reader may now try and ask the question "What does this do?". The type class approach is meant to limit the amount of Data types we inherently recognise as defaults or primitives.

This allows for a very simple limitation mechanism where we exploit the basic Scala implicit resolution mechanism to perform efficient type restrictions and encoding/decoding to/from database results. If a type needs serialisation, we simply request for type evidence via the below type class using implicity[SQLPrimitive[T]]{code}.

If proof exists that the type T has an SQLPrimitive type class associated with it, then the type is considered primitive with regards to the current SQL database in use. This means we will allow for variation of primitive type implementations between different SQL databases. The challenge arises from needing to parse Primitives implicitly in the DSL module itself to create the basic extendable functionality.

We then need to allow other database specific implementations to override these implementations and pass the new ones explicity. As this encapsulates very important information, such as how to decode a specific type from a given database implementation when a query is performed, the breach of this contract means we might as well start another project.

Any below weirdness or poor choice of semantics is probably the only possible way through which the above was achieved This involves defining the default extendable types as normal classes instead of traits to allow their instantiation as overridable vals.