AdvancedMeta
Related Doc:
package meta
Source JDBC types from which values of type A can be read.
Source JDBC types from which values of type A can be read.
Destination JDBC types to which values of type A can be written.
Destination JDBC types to which values of type A can be written.
Name of the Scala type, for diagnostic purposes.
Name of the Scala type, for diagnostic purposes. Smart constructors require a TypeTag to
guarantee this value is correct.
List of schema types to which values of type A can be written and from which they can be
read.
List of schema types to which values of type A can be written and from which they can be
read. Databases will often have several names for the same type, and the JDBC driver may
report an alias that doesn't appear in the schema or indeed in the database documentation.
This field is therefore a list.
True if A can be read from a column or 'out' parameter with the specified JdbcType and
schema types.
True if A can be written to a column or 'in' parameter with the specified JdbcType and
schema types.
Switch on the flavor of this Meta.
Switch on the flavor of this Meta.
Invariant map.
Invariant map.
Invariant map with null handling, for A, B >: Null; the functions f and g will
never be passed a null value.
Invariant map with null handling, for A, B >: Null; the functions f and g will
never be passed a null value.
(Since version 0.4.2) Null is no longer observable here; just use xmap.
Metafor "advanced" JDBC types as defined by the specification. These includeArray,JavaObject,Struct, and other types that require driver, schema, or vendor-specific knowledge and are unlikely to be portable between vendors (or indeed between applications). These mappings require (in addition to matching JDBC types) matching driver, schema, or vendor-specific data types, sadly given asStrings in JDBC.