generated code - do not edit.

NewDBLite creates a new instance of DBLite.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

this field is used during the restauration process.

ALTERNATIVE_IDAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model alternative_idAPI.

ALTERNATIVE_IDDB describes a alternative_id in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model alternative_idDB.

ALTERNATIVE_IDDBResponse provides response swagger:response alternative_idDBResponse.

ALTERNATIVE_IDPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ALTERNATIVE_IDWOP is a ALTERNATIVE_ID without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

AnyTypeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model anytypeAPI.

AnyTypeDB describes a anytype in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model anytypeDB.

AnyTypeDBResponse provides response swagger:response anytypeDBResponse.

AnyTypePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

AnyTypeWOP is a AnyType without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_booleanAPI.

ATTRIBUTE_DEFINITION_BOOLEANDB describes a attribute_definition_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_booleanDB.

ATTRIBUTE_DEFINITION_BOOLEANDBResponse provides response swagger:response attribute_definition_booleanDBResponse.

ATTRIBUTE_DEFINITION_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_BOOLEANWOP is a ATTRIBUTE_DEFINITION_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_dateAPI.

ATTRIBUTE_DEFINITION_DATEDB describes a attribute_definition_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_dateDB.

ATTRIBUTE_DEFINITION_DATEDBResponse provides response swagger:response attribute_definition_dateDBResponse.

ATTRIBUTE_DEFINITION_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_DATEWOP is a ATTRIBUTE_DEFINITION_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_enumerationAPI.

ATTRIBUTE_DEFINITION_ENUMERATIONDB describes a attribute_definition_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_enumerationDB.

ATTRIBUTE_DEFINITION_ENUMERATIONDBResponse provides response swagger:response attribute_definition_enumerationDBResponse.

ATTRIBUTE_DEFINITION_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_ENUMERATIONWOP is a ATTRIBUTE_DEFINITION_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_integerAPI.

ATTRIBUTE_DEFINITION_INTEGERDB describes a attribute_definition_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_integerDB.

ATTRIBUTE_DEFINITION_INTEGERDBResponse provides response swagger:response attribute_definition_integerDBResponse.

ATTRIBUTE_DEFINITION_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_INTEGERWOP is a ATTRIBUTE_DEFINITION_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_realAPI.

ATTRIBUTE_DEFINITION_REALDB describes a attribute_definition_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_realDB.

ATTRIBUTE_DEFINITION_REALDBResponse provides response swagger:response attribute_definition_realDBResponse.

ATTRIBUTE_DEFINITION_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_REALWOP is a ATTRIBUTE_DEFINITION_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_stringAPI.

ATTRIBUTE_DEFINITION_STRINGDB describes a attribute_definition_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_stringDB.

ATTRIBUTE_DEFINITION_STRINGDBResponse provides response swagger:response attribute_definition_stringDBResponse.

ATTRIBUTE_DEFINITION_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_STRINGWOP is a ATTRIBUTE_DEFINITION_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_DEFINITION_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_definition_xhtmlAPI.

ATTRIBUTE_DEFINITION_XHTMLDB describes a attribute_definition_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_definition_xhtmlDB.

ATTRIBUTE_DEFINITION_XHTMLDBResponse provides response swagger:response attribute_definition_xhtmlDBResponse.

ATTRIBUTE_DEFINITION_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_DEFINITION_XHTMLWOP is a ATTRIBUTE_DEFINITION_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_booleanAPI.

ATTRIBUTE_VALUE_BOOLEANDB describes a attribute_value_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_booleanDB.

ATTRIBUTE_VALUE_BOOLEANDBResponse provides response swagger:response attribute_value_booleanDBResponse.

ATTRIBUTE_VALUE_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_BOOLEANWOP is a ATTRIBUTE_VALUE_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_dateAPI.

ATTRIBUTE_VALUE_DATEDB describes a attribute_value_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_dateDB.

ATTRIBUTE_VALUE_DATEDBResponse provides response swagger:response attribute_value_dateDBResponse.

ATTRIBUTE_VALUE_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_DATEWOP is a ATTRIBUTE_VALUE_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_enumerationAPI.

ATTRIBUTE_VALUE_ENUMERATIONDB describes a attribute_value_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_enumerationDB.

ATTRIBUTE_VALUE_ENUMERATIONDBResponse provides response swagger:response attribute_value_enumerationDBResponse.

ATTRIBUTE_VALUE_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_ENUMERATIONWOP is a ATTRIBUTE_VALUE_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_integerAPI.

ATTRIBUTE_VALUE_INTEGERDB describes a attribute_value_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_integerDB.

ATTRIBUTE_VALUE_INTEGERDBResponse provides response swagger:response attribute_value_integerDBResponse.

ATTRIBUTE_VALUE_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_INTEGERWOP is a ATTRIBUTE_VALUE_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_realAPI.

ATTRIBUTE_VALUE_REALDB describes a attribute_value_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_realDB.

ATTRIBUTE_VALUE_REALDBResponse provides response swagger:response attribute_value_realDBResponse.

ATTRIBUTE_VALUE_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_REALWOP is a ATTRIBUTE_VALUE_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_stringAPI.

ATTRIBUTE_VALUE_STRINGDB describes a attribute_value_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_stringDB.

ATTRIBUTE_VALUE_STRINGDBResponse provides response swagger:response attribute_value_stringDBResponse.

ATTRIBUTE_VALUE_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_STRINGWOP is a ATTRIBUTE_VALUE_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ATTRIBUTE_VALUE_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model attribute_value_xhtmlAPI.

ATTRIBUTE_VALUE_XHTMLDB describes a attribute_value_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model attribute_value_xhtmlDB.

ATTRIBUTE_VALUE_XHTMLDBResponse provides response swagger:response attribute_value_xhtmlDBResponse.

ATTRIBUTE_VALUE_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ATTRIBUTE_VALUE_XHTMLWOP is a ATTRIBUTE_VALUE_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

BackRepoStruct supports callback functions.

DATATYPE_DEFINITION_BOOLEANAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_booleanAPI.

DATATYPE_DEFINITION_BOOLEANDB describes a datatype_definition_boolean in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_booleanDB.

DATATYPE_DEFINITION_BOOLEANDBResponse provides response swagger:response datatype_definition_booleanDBResponse.

DATATYPE_DEFINITION_BOOLEANPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_BOOLEANWOP is a DATATYPE_DEFINITION_BOOLEAN without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_DATEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_dateAPI.

DATATYPE_DEFINITION_DATEDB describes a datatype_definition_date in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_dateDB.

DATATYPE_DEFINITION_DATEDBResponse provides response swagger:response datatype_definition_dateDBResponse.

DATATYPE_DEFINITION_DATEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_DATEWOP is a DATATYPE_DEFINITION_DATE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_ENUMERATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_enumerationAPI.

DATATYPE_DEFINITION_ENUMERATIONDB describes a datatype_definition_enumeration in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_enumerationDB.

DATATYPE_DEFINITION_ENUMERATIONDBResponse provides response swagger:response datatype_definition_enumerationDBResponse.

DATATYPE_DEFINITION_ENUMERATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_ENUMERATIONWOP is a DATATYPE_DEFINITION_ENUMERATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_INTEGERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_integerAPI.

DATATYPE_DEFINITION_INTEGERDB describes a datatype_definition_integer in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_integerDB.

DATATYPE_DEFINITION_INTEGERDBResponse provides response swagger:response datatype_definition_integerDBResponse.

DATATYPE_DEFINITION_INTEGERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_INTEGERWOP is a DATATYPE_DEFINITION_INTEGER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_REALAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_realAPI.

DATATYPE_DEFINITION_REALDB describes a datatype_definition_real in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_realDB.

DATATYPE_DEFINITION_REALDBResponse provides response swagger:response datatype_definition_realDBResponse.

DATATYPE_DEFINITION_REALPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_REALWOP is a DATATYPE_DEFINITION_REAL without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_STRINGAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_stringAPI.

DATATYPE_DEFINITION_STRINGDB describes a datatype_definition_string in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_stringDB.

DATATYPE_DEFINITION_STRINGDBResponse provides response swagger:response datatype_definition_stringDBResponse.

DATATYPE_DEFINITION_STRINGPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_STRINGWOP is a DATATYPE_DEFINITION_STRING without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DATATYPE_DEFINITION_XHTMLAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model datatype_definition_xhtmlAPI.

DATATYPE_DEFINITION_XHTMLDB describes a datatype_definition_xhtml in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model datatype_definition_xhtmlDB.

DATATYPE_DEFINITION_XHTMLDBResponse provides response swagger:response datatype_definition_xhtmlDBResponse.

DATATYPE_DEFINITION_XHTMLPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

DATATYPE_DEFINITION_XHTMLWOP is a DATATYPE_DEFINITION_XHTML without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

DBLite is an in-memory database implementation of DBInterface.

EMBEDDED_VALUEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model embedded_valueAPI.

EMBEDDED_VALUEDB describes a embedded_value in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model embedded_valueDB.

EMBEDDED_VALUEDBResponse provides response swagger:response embedded_valueDBResponse.

EMBEDDED_VALUEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

EMBEDDED_VALUEWOP is a EMBEDDED_VALUE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ENUM_VALUEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model enum_valueAPI.

ENUM_VALUEDB describes a enum_value in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model enum_valueDB.

ENUM_VALUEDBResponse provides response swagger:response enum_valueDBResponse.

ENUM_VALUEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

ENUM_VALUEWOP is a ENUM_VALUE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

RELATION_GROUP_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model relation_group_typeAPI.

RELATION_GROUP_TYPEDB describes a relation_group_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model relation_group_typeDB.

RELATION_GROUP_TYPEDBResponse provides response swagger:response relation_group_typeDBResponse.

RELATION_GROUP_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

RELATION_GROUP_TYPEWOP is a RELATION_GROUP_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

RELATION_GROUPAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model relation_groupAPI.

RELATION_GROUPDB describes a relation_group in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model relation_groupDB.

RELATION_GROUPDBResponse provides response swagger:response relation_groupDBResponse.

RELATION_GROUPPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

RELATION_GROUPWOP is a RELATION_GROUP without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_CONTENTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_contentAPI.

REQ_IF_CONTENTDB describes a req_if_content in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_contentDB.

REQ_IF_CONTENTDBResponse provides response swagger:response req_if_contentDBResponse.

REQ_IF_CONTENTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_CONTENTWOP is a REQ_IF_CONTENT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_HEADERAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_headerAPI.

REQ_IF_HEADERDB describes a req_if_header in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_headerDB.

REQ_IF_HEADERDBResponse provides response swagger:response req_if_headerDBResponse.

REQ_IF_HEADERPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_HEADERWOP is a REQ_IF_HEADER without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IF_TOOL_EXTENSIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_if_tool_extensionAPI.

REQ_IF_TOOL_EXTENSIONDB describes a req_if_tool_extension in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_if_tool_extensionDB.

REQ_IF_TOOL_EXTENSIONDBResponse provides response swagger:response req_if_tool_extensionDBResponse.

REQ_IF_TOOL_EXTENSIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IF_TOOL_EXTENSIONWOP is a REQ_IF_TOOL_EXTENSION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

REQ_IFAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model req_ifAPI.

REQ_IFDB describes a req_if in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model req_ifDB.

REQ_IFDBResponse provides response swagger:response req_ifDBResponse.

REQ_IFPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

REQ_IFWOP is a REQ_IF without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_HIERARCHYAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_hierarchyAPI.

SPEC_HIERARCHYDB describes a spec_hierarchy in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_hierarchyDB.

SPEC_HIERARCHYDBResponse provides response swagger:response spec_hierarchyDBResponse.

SPEC_HIERARCHYPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_HIERARCHYWOP is a SPEC_HIERARCHY without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_OBJECT_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_object_typeAPI.

SPEC_OBJECT_TYPEDB describes a spec_object_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_object_typeDB.

SPEC_OBJECT_TYPEDBResponse provides response swagger:response spec_object_typeDBResponse.

SPEC_OBJECT_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_OBJECT_TYPEWOP is a SPEC_OBJECT_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_OBJECTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_objectAPI.

SPEC_OBJECTDB describes a spec_object in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_objectDB.

SPEC_OBJECTDBResponse provides response swagger:response spec_objectDBResponse.

SPEC_OBJECTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_OBJECTWOP is a SPEC_OBJECT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_RELATION_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_relation_typeAPI.

SPEC_RELATION_TYPEDB describes a spec_relation_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_relation_typeDB.

SPEC_RELATION_TYPEDBResponse provides response swagger:response spec_relation_typeDBResponse.

SPEC_RELATION_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_RELATION_TYPEWOP is a SPEC_RELATION_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPEC_RELATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model spec_relationAPI.

SPEC_RELATIONDB describes a spec_relation in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model spec_relationDB.

SPEC_RELATIONDBResponse provides response swagger:response spec_relationDBResponse.

SPEC_RELATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPEC_RELATIONWOP is a SPEC_RELATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPECIFICATION_TYPEAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model specification_typeAPI.

SPECIFICATION_TYPEDB describes a specification_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model specification_typeDB.

SPECIFICATION_TYPEDBResponse provides response swagger:response specification_typeDBResponse.

SPECIFICATION_TYPEPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPECIFICATION_TYPEWOP is a SPECIFICATION_TYPE without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

SPECIFICATIONAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model specificationAPI.

SPECIFICATIONDB describes a specification in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model specificationDB.

SPECIFICATIONDBResponse provides response swagger:response specificationDBResponse.

SPECIFICATIONPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

SPECIFICATIONWOP is a SPECIFICATION without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_a_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_a_typeAPI.

Xhtml_a_typeDB describes a xhtml_a_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_a_typeDB.

Xhtml_a_typeDBResponse provides response swagger:response xhtml_a_typeDBResponse.

Xhtml_a_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_a_typeWOP is a Xhtml_a_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_abbr_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_abbr_typeAPI.

Xhtml_abbr_typeDB describes a xhtml_abbr_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_abbr_typeDB.

Xhtml_abbr_typeDBResponse provides response swagger:response xhtml_abbr_typeDBResponse.

Xhtml_abbr_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_abbr_typeWOP is a Xhtml_abbr_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_acronym_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_acronym_typeAPI.

Xhtml_acronym_typeDB describes a xhtml_acronym_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_acronym_typeDB.

Xhtml_acronym_typeDBResponse provides response swagger:response xhtml_acronym_typeDBResponse.

Xhtml_acronym_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_acronym_typeWOP is a Xhtml_acronym_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_address_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_address_typeAPI.

Xhtml_address_typeDB describes a xhtml_address_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_address_typeDB.

Xhtml_address_typeDBResponse provides response swagger:response xhtml_address_typeDBResponse.

Xhtml_address_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_address_typeWOP is a Xhtml_address_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_blockquote_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_blockquote_typeAPI.

Xhtml_blockquote_typeDB describes a xhtml_blockquote_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_blockquote_typeDB.

Xhtml_blockquote_typeDBResponse provides response swagger:response xhtml_blockquote_typeDBResponse.

Xhtml_blockquote_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_blockquote_typeWOP is a Xhtml_blockquote_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_br_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_br_typeAPI.

Xhtml_br_typeDB describes a xhtml_br_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_br_typeDB.

Xhtml_br_typeDBResponse provides response swagger:response xhtml_br_typeDBResponse.

Xhtml_br_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_br_typeWOP is a Xhtml_br_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_caption_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_caption_typeAPI.

Xhtml_caption_typeDB describes a xhtml_caption_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_caption_typeDB.

Xhtml_caption_typeDBResponse provides response swagger:response xhtml_caption_typeDBResponse.

Xhtml_caption_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_caption_typeWOP is a Xhtml_caption_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_cite_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_cite_typeAPI.

Xhtml_cite_typeDB describes a xhtml_cite_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_cite_typeDB.

Xhtml_cite_typeDBResponse provides response swagger:response xhtml_cite_typeDBResponse.

Xhtml_cite_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_cite_typeWOP is a Xhtml_cite_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_code_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_code_typeAPI.

Xhtml_code_typeDB describes a xhtml_code_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_code_typeDB.

Xhtml_code_typeDBResponse provides response swagger:response xhtml_code_typeDBResponse.

Xhtml_code_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_code_typeWOP is a Xhtml_code_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_col_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_col_typeAPI.

Xhtml_col_typeDB describes a xhtml_col_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_col_typeDB.

Xhtml_col_typeDBResponse provides response swagger:response xhtml_col_typeDBResponse.

Xhtml_col_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_col_typeWOP is a Xhtml_col_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_colgroup_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_colgroup_typeAPI.

Xhtml_colgroup_typeDB describes a xhtml_colgroup_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_colgroup_typeDB.

Xhtml_colgroup_typeDBResponse provides response swagger:response xhtml_colgroup_typeDBResponse.

Xhtml_colgroup_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_colgroup_typeWOP is a Xhtml_colgroup_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

XHTML_CONTENTAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_contentAPI.

XHTML_CONTENTDB describes a xhtml_content in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_contentDB.

XHTML_CONTENTDBResponse provides response swagger:response xhtml_contentDBResponse.

XHTML_CONTENTPointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

XHTML_CONTENTWOP is a XHTML_CONTENT without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_dd_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_dd_typeAPI.

Xhtml_dd_typeDB describes a xhtml_dd_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_dd_typeDB.

Xhtml_dd_typeDBResponse provides response swagger:response xhtml_dd_typeDBResponse.

Xhtml_dd_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_dd_typeWOP is a Xhtml_dd_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_dfn_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_dfn_typeAPI.

Xhtml_dfn_typeDB describes a xhtml_dfn_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_dfn_typeDB.

Xhtml_dfn_typeDBResponse provides response swagger:response xhtml_dfn_typeDBResponse.

Xhtml_dfn_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_dfn_typeWOP is a Xhtml_dfn_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_div_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_div_typeAPI.

Xhtml_div_typeDB describes a xhtml_div_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_div_typeDB.

Xhtml_div_typeDBResponse provides response swagger:response xhtml_div_typeDBResponse.

Xhtml_div_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_div_typeWOP is a Xhtml_div_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_dl_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_dl_typeAPI.

Xhtml_dl_typeDB describes a xhtml_dl_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_dl_typeDB.

Xhtml_dl_typeDBResponse provides response swagger:response xhtml_dl_typeDBResponse.

Xhtml_dl_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_dl_typeWOP is a Xhtml_dl_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_dt_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_dt_typeAPI.

Xhtml_dt_typeDB describes a xhtml_dt_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_dt_typeDB.

Xhtml_dt_typeDBResponse provides response swagger:response xhtml_dt_typeDBResponse.

Xhtml_dt_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_dt_typeWOP is a Xhtml_dt_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_edit_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_edit_typeAPI.

Xhtml_edit_typeDB describes a xhtml_edit_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_edit_typeDB.

Xhtml_edit_typeDBResponse provides response swagger:response xhtml_edit_typeDBResponse.

Xhtml_edit_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_edit_typeWOP is a Xhtml_edit_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_em_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_em_typeAPI.

Xhtml_em_typeDB describes a xhtml_em_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_em_typeDB.

Xhtml_em_typeDBResponse provides response swagger:response xhtml_em_typeDBResponse.

Xhtml_em_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_em_typeWOP is a Xhtml_em_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h1_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h1_typeAPI.

Xhtml_h1_typeDB describes a xhtml_h1_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h1_typeDB.

Xhtml_h1_typeDBResponse provides response swagger:response xhtml_h1_typeDBResponse.

Xhtml_h1_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h1_typeWOP is a Xhtml_h1_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h2_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h2_typeAPI.

Xhtml_h2_typeDB describes a xhtml_h2_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h2_typeDB.

Xhtml_h2_typeDBResponse provides response swagger:response xhtml_h2_typeDBResponse.

Xhtml_h2_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h2_typeWOP is a Xhtml_h2_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h3_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h3_typeAPI.

Xhtml_h3_typeDB describes a xhtml_h3_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h3_typeDB.

Xhtml_h3_typeDBResponse provides response swagger:response xhtml_h3_typeDBResponse.

Xhtml_h3_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h3_typeWOP is a Xhtml_h3_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h4_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h4_typeAPI.

Xhtml_h4_typeDB describes a xhtml_h4_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h4_typeDB.

Xhtml_h4_typeDBResponse provides response swagger:response xhtml_h4_typeDBResponse.

Xhtml_h4_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h4_typeWOP is a Xhtml_h4_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h5_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h5_typeAPI.

Xhtml_h5_typeDB describes a xhtml_h5_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h5_typeDB.

Xhtml_h5_typeDBResponse provides response swagger:response xhtml_h5_typeDBResponse.

Xhtml_h5_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h5_typeWOP is a Xhtml_h5_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_h6_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_h6_typeAPI.

Xhtml_h6_typeDB describes a xhtml_h6_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_h6_typeDB.

Xhtml_h6_typeDBResponse provides response swagger:response xhtml_h6_typeDBResponse.

Xhtml_h6_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_h6_typeWOP is a Xhtml_h6_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_heading_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_heading_typeAPI.

Xhtml_heading_typeDB describes a xhtml_heading_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_heading_typeDB.

Xhtml_heading_typeDBResponse provides response swagger:response xhtml_heading_typeDBResponse.

Xhtml_heading_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_heading_typeWOP is a Xhtml_heading_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_hr_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_hr_typeAPI.

Xhtml_hr_typeDB describes a xhtml_hr_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_hr_typeDB.

Xhtml_hr_typeDBResponse provides response swagger:response xhtml_hr_typeDBResponse.

Xhtml_hr_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_hr_typeWOP is a Xhtml_hr_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_InlPres_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_inlpres_typeAPI.

Xhtml_InlPres_typeDB describes a xhtml_inlpres_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_inlpres_typeDB.

Xhtml_InlPres_typeDBResponse provides response swagger:response xhtml_inlpres_typeDBResponse.

Xhtml_InlPres_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_InlPres_typeWOP is a Xhtml_InlPres_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_kbd_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_kbd_typeAPI.

Xhtml_kbd_typeDB describes a xhtml_kbd_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_kbd_typeDB.

Xhtml_kbd_typeDBResponse provides response swagger:response xhtml_kbd_typeDBResponse.

Xhtml_kbd_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_kbd_typeWOP is a Xhtml_kbd_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_li_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_li_typeAPI.

Xhtml_li_typeDB describes a xhtml_li_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_li_typeDB.

Xhtml_li_typeDBResponse provides response swagger:response xhtml_li_typeDBResponse.

Xhtml_li_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_li_typeWOP is a Xhtml_li_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_object_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_object_typeAPI.

Xhtml_object_typeDB describes a xhtml_object_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_object_typeDB.

Xhtml_object_typeDBResponse provides response swagger:response xhtml_object_typeDBResponse.

Xhtml_object_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_object_typeWOP is a Xhtml_object_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_ol_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_ol_typeAPI.

Xhtml_ol_typeDB describes a xhtml_ol_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_ol_typeDB.

Xhtml_ol_typeDBResponse provides response swagger:response xhtml_ol_typeDBResponse.

Xhtml_ol_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_ol_typeWOP is a Xhtml_ol_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_p_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_p_typeAPI.

Xhtml_p_typeDB describes a xhtml_p_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_p_typeDB.

Xhtml_p_typeDBResponse provides response swagger:response xhtml_p_typeDBResponse.

Xhtml_p_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_p_typeWOP is a Xhtml_p_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_param_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_param_typeAPI.

Xhtml_param_typeDB describes a xhtml_param_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_param_typeDB.

Xhtml_param_typeDBResponse provides response swagger:response xhtml_param_typeDBResponse.

Xhtml_param_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_param_typeWOP is a Xhtml_param_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_pre_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_pre_typeAPI.

Xhtml_pre_typeDB describes a xhtml_pre_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_pre_typeDB.

Xhtml_pre_typeDBResponse provides response swagger:response xhtml_pre_typeDBResponse.

Xhtml_pre_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_pre_typeWOP is a Xhtml_pre_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_q_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_q_typeAPI.

Xhtml_q_typeDB describes a xhtml_q_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_q_typeDB.

Xhtml_q_typeDBResponse provides response swagger:response xhtml_q_typeDBResponse.

Xhtml_q_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_q_typeWOP is a Xhtml_q_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_samp_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_samp_typeAPI.

Xhtml_samp_typeDB describes a xhtml_samp_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_samp_typeDB.

Xhtml_samp_typeDBResponse provides response swagger:response xhtml_samp_typeDBResponse.

Xhtml_samp_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_samp_typeWOP is a Xhtml_samp_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_span_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_span_typeAPI.

Xhtml_span_typeDB describes a xhtml_span_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_span_typeDB.

Xhtml_span_typeDBResponse provides response swagger:response xhtml_span_typeDBResponse.

Xhtml_span_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_span_typeWOP is a Xhtml_span_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_strong_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_strong_typeAPI.

Xhtml_strong_typeDB describes a xhtml_strong_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_strong_typeDB.

Xhtml_strong_typeDBResponse provides response swagger:response xhtml_strong_typeDBResponse.

Xhtml_strong_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_strong_typeWOP is a Xhtml_strong_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_table_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_table_typeAPI.

Xhtml_table_typeDB describes a xhtml_table_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_table_typeDB.

Xhtml_table_typeDBResponse provides response swagger:response xhtml_table_typeDBResponse.

Xhtml_table_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_table_typeWOP is a Xhtml_table_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_tbody_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_tbody_typeAPI.

Xhtml_tbody_typeDB describes a xhtml_tbody_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_tbody_typeDB.

Xhtml_tbody_typeDBResponse provides response swagger:response xhtml_tbody_typeDBResponse.

Xhtml_tbody_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_tbody_typeWOP is a Xhtml_tbody_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_td_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_td_typeAPI.

Xhtml_td_typeDB describes a xhtml_td_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_td_typeDB.

Xhtml_td_typeDBResponse provides response swagger:response xhtml_td_typeDBResponse.

Xhtml_td_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_td_typeWOP is a Xhtml_td_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_tfoot_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_tfoot_typeAPI.

Xhtml_tfoot_typeDB describes a xhtml_tfoot_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_tfoot_typeDB.

Xhtml_tfoot_typeDBResponse provides response swagger:response xhtml_tfoot_typeDBResponse.

Xhtml_tfoot_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_tfoot_typeWOP is a Xhtml_tfoot_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_th_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_th_typeAPI.

Xhtml_th_typeDB describes a xhtml_th_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_th_typeDB.

Xhtml_th_typeDBResponse provides response swagger:response xhtml_th_typeDBResponse.

Xhtml_th_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_th_typeWOP is a Xhtml_th_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_thead_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_thead_typeAPI.

Xhtml_thead_typeDB describes a xhtml_thead_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_thead_typeDB.

Xhtml_thead_typeDBResponse provides response swagger:response xhtml_thead_typeDBResponse.

Xhtml_thead_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_thead_typeWOP is a Xhtml_thead_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_tr_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_tr_typeAPI.

Xhtml_tr_typeDB describes a xhtml_tr_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_tr_typeDB.

Xhtml_tr_typeDBResponse provides response swagger:response xhtml_tr_typeDBResponse.

Xhtml_tr_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_tr_typeWOP is a Xhtml_tr_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_ul_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_ul_typeAPI.

Xhtml_ul_typeDB describes a xhtml_ul_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_ul_typeDB.

Xhtml_ul_typeDBResponse provides response swagger:response xhtml_ul_typeDBResponse.

Xhtml_ul_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_ul_typeWOP is a Xhtml_ul_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

Xhtml_var_typeAPI is the input in POST API for POST, API, one needs the fields of the model as well as the fields from associations ("Has One" and "Has Many") that are generated to fullfill the ORM requirements for associations swagger:model xhtml_var_typeAPI.

Xhtml_var_typeDB describes a xhtml_var_type in the database It incorporates the GORM ID, basic fields from the model (because they can be serialized), the encoded version of pointers swagger:model xhtml_var_typeDB.

Xhtml_var_typeDBResponse provides response swagger:response xhtml_var_typeDBResponse.

Xhtml_var_typePointersEncoding encodes pointers to Struct and reverse pointers of slice of poitners to Struct.

Xhtml_var_typeWOP is a Xhtml_var_type without pointers (WOP is an acronym for "Without Pointers") it holds the same basic fields but pointers are encoded into uint.

ALTERNATIVE_IDDBs arrays alternative_idDBs swagger:response alternative_idDBsResponse.

AnyTypeDBs arrays anytypeDBs swagger:response anytypeDBsResponse.

ATTRIBUTE_DEFINITION_BOOLEANDBs arrays attribute_definition_booleanDBs swagger:response attribute_definition_booleanDBsResponse.

ATTRIBUTE_DEFINITION_DATEDBs arrays attribute_definition_dateDBs swagger:response attribute_definition_dateDBsResponse.

ATTRIBUTE_DEFINITION_ENUMERATIONDBs arrays attribute_definition_enumerationDBs swagger:response attribute_definition_enumerationDBsResponse.

ATTRIBUTE_DEFINITION_INTEGERDBs arrays attribute_definition_integerDBs swagger:response attribute_definition_integerDBsResponse.

ATTRIBUTE_DEFINITION_REALDBs arrays attribute_definition_realDBs swagger:response attribute_definition_realDBsResponse.

ATTRIBUTE_DEFINITION_STRINGDBs arrays attribute_definition_stringDBs swagger:response attribute_definition_stringDBsResponse.

ATTRIBUTE_DEFINITION_XHTMLDBs arrays attribute_definition_xhtmlDBs swagger:response attribute_definition_xhtmlDBsResponse.

ATTRIBUTE_VALUE_BOOLEANDBs arrays attribute_value_booleanDBs swagger:response attribute_value_booleanDBsResponse.

ATTRIBUTE_VALUE_DATEDBs arrays attribute_value_dateDBs swagger:response attribute_value_dateDBsResponse.

ATTRIBUTE_VALUE_ENUMERATIONDBs arrays attribute_value_enumerationDBs swagger:response attribute_value_enumerationDBsResponse.

ATTRIBUTE_VALUE_INTEGERDBs arrays attribute_value_integerDBs swagger:response attribute_value_integerDBsResponse.

ATTRIBUTE_VALUE_REALDBs arrays attribute_value_realDBs swagger:response attribute_value_realDBsResponse.

ATTRIBUTE_VALUE_STRINGDBs arrays attribute_value_stringDBs swagger:response attribute_value_stringDBsResponse.

ATTRIBUTE_VALUE_XHTMLDBs arrays attribute_value_xhtmlDBs swagger:response attribute_value_xhtmlDBsResponse.

DATATYPE_DEFINITION_BOOLEANDBs arrays datatype_definition_booleanDBs swagger:response datatype_definition_booleanDBsResponse.

DATATYPE_DEFINITION_DATEDBs arrays datatype_definition_dateDBs swagger:response datatype_definition_dateDBsResponse.

DATATYPE_DEFINITION_ENUMERATIONDBs arrays datatype_definition_enumerationDBs swagger:response datatype_definition_enumerationDBsResponse.

DATATYPE_DEFINITION_INTEGERDBs arrays datatype_definition_integerDBs swagger:response datatype_definition_integerDBsResponse.

DATATYPE_DEFINITION_REALDBs arrays datatype_definition_realDBs swagger:response datatype_definition_realDBsResponse.

DATATYPE_DEFINITION_STRINGDBs arrays datatype_definition_stringDBs swagger:response datatype_definition_stringDBsResponse.

DATATYPE_DEFINITION_XHTMLDBs arrays datatype_definition_xhtmlDBs swagger:response datatype_definition_xhtmlDBsResponse.

EMBEDDED_VALUEDBs arrays embedded_valueDBs swagger:response embedded_valueDBsResponse.

ENUM_VALUEDBs arrays enum_valueDBs swagger:response enum_valueDBsResponse.

RELATION_GROUP_TYPEDBs arrays relation_group_typeDBs swagger:response relation_group_typeDBsResponse.

RELATION_GROUPDBs arrays relation_groupDBs swagger:response relation_groupDBsResponse.

REQ_IF_CONTENTDBs arrays req_if_contentDBs swagger:response req_if_contentDBsResponse.

REQ_IF_HEADERDBs arrays req_if_headerDBs swagger:response req_if_headerDBsResponse.

REQ_IF_TOOL_EXTENSIONDBs arrays req_if_tool_extensionDBs swagger:response req_if_tool_extensionDBsResponse.

REQ_IFDBs arrays req_ifDBs swagger:response req_ifDBsResponse.

SPEC_HIERARCHYDBs arrays spec_hierarchyDBs swagger:response spec_hierarchyDBsResponse.

SPEC_OBJECT_TYPEDBs arrays spec_object_typeDBs swagger:response spec_object_typeDBsResponse.

SPEC_OBJECTDBs arrays spec_objectDBs swagger:response spec_objectDBsResponse.

SPEC_RELATION_TYPEDBs arrays spec_relation_typeDBs swagger:response spec_relation_typeDBsResponse.

SPEC_RELATIONDBs arrays spec_relationDBs swagger:response spec_relationDBsResponse.

SPECIFICATION_TYPEDBs arrays specification_typeDBs swagger:response specification_typeDBsResponse.

SPECIFICATIONDBs arrays specificationDBs swagger:response specificationDBsResponse.

Xhtml_a_typeDBs arrays xhtml_a_typeDBs swagger:response xhtml_a_typeDBsResponse.

Xhtml_abbr_typeDBs arrays xhtml_abbr_typeDBs swagger:response xhtml_abbr_typeDBsResponse.

Xhtml_acronym_typeDBs arrays xhtml_acronym_typeDBs swagger:response xhtml_acronym_typeDBsResponse.

Xhtml_address_typeDBs arrays xhtml_address_typeDBs swagger:response xhtml_address_typeDBsResponse.

Xhtml_blockquote_typeDBs arrays xhtml_blockquote_typeDBs swagger:response xhtml_blockquote_typeDBsResponse.

Xhtml_br_typeDBs arrays xhtml_br_typeDBs swagger:response xhtml_br_typeDBsResponse.

Xhtml_caption_typeDBs arrays xhtml_caption_typeDBs swagger:response xhtml_caption_typeDBsResponse.

Xhtml_cite_typeDBs arrays xhtml_cite_typeDBs swagger:response xhtml_cite_typeDBsResponse.

Xhtml_code_typeDBs arrays xhtml_code_typeDBs swagger:response xhtml_code_typeDBsResponse.

Xhtml_col_typeDBs arrays xhtml_col_typeDBs swagger:response xhtml_col_typeDBsResponse.

Xhtml_colgroup_typeDBs arrays xhtml_colgroup_typeDBs swagger:response xhtml_colgroup_typeDBsResponse.

XHTML_CONTENTDBs arrays xhtml_contentDBs swagger:response xhtml_contentDBsResponse.

Xhtml_dd_typeDBs arrays xhtml_dd_typeDBs swagger:response xhtml_dd_typeDBsResponse.

Xhtml_dfn_typeDBs arrays xhtml_dfn_typeDBs swagger:response xhtml_dfn_typeDBsResponse.

Xhtml_div_typeDBs arrays xhtml_div_typeDBs swagger:response xhtml_div_typeDBsResponse.

Xhtml_dl_typeDBs arrays xhtml_dl_typeDBs swagger:response xhtml_dl_typeDBsResponse.

Xhtml_dt_typeDBs arrays xhtml_dt_typeDBs swagger:response xhtml_dt_typeDBsResponse.

Xhtml_edit_typeDBs arrays xhtml_edit_typeDBs swagger:response xhtml_edit_typeDBsResponse.

Xhtml_em_typeDBs arrays xhtml_em_typeDBs swagger:response xhtml_em_typeDBsResponse.

Xhtml_h1_typeDBs arrays xhtml_h1_typeDBs swagger:response xhtml_h1_typeDBsResponse.

Xhtml_h2_typeDBs arrays xhtml_h2_typeDBs swagger:response xhtml_h2_typeDBsResponse.

Xhtml_h3_typeDBs arrays xhtml_h3_typeDBs swagger:response xhtml_h3_typeDBsResponse.

Xhtml_h4_typeDBs arrays xhtml_h4_typeDBs swagger:response xhtml_h4_typeDBsResponse.

Xhtml_h5_typeDBs arrays xhtml_h5_typeDBs swagger:response xhtml_h5_typeDBsResponse.

Xhtml_h6_typeDBs arrays xhtml_h6_typeDBs swagger:response xhtml_h6_typeDBsResponse.

Xhtml_heading_typeDBs arrays xhtml_heading_typeDBs swagger:response xhtml_heading_typeDBsResponse.

Xhtml_hr_typeDBs arrays xhtml_hr_typeDBs swagger:response xhtml_hr_typeDBsResponse.

Xhtml_InlPres_typeDBs arrays xhtml_inlpres_typeDBs swagger:response xhtml_inlpres_typeDBsResponse.

Xhtml_kbd_typeDBs arrays xhtml_kbd_typeDBs swagger:response xhtml_kbd_typeDBsResponse.

Xhtml_li_typeDBs arrays xhtml_li_typeDBs swagger:response xhtml_li_typeDBsResponse.

Xhtml_object_typeDBs arrays xhtml_object_typeDBs swagger:response xhtml_object_typeDBsResponse.

Xhtml_ol_typeDBs arrays xhtml_ol_typeDBs swagger:response xhtml_ol_typeDBsResponse.

Xhtml_p_typeDBs arrays xhtml_p_typeDBs swagger:response xhtml_p_typeDBsResponse.

Xhtml_param_typeDBs arrays xhtml_param_typeDBs swagger:response xhtml_param_typeDBsResponse.

Xhtml_pre_typeDBs arrays xhtml_pre_typeDBs swagger:response xhtml_pre_typeDBsResponse.

Xhtml_q_typeDBs arrays xhtml_q_typeDBs swagger:response xhtml_q_typeDBsResponse.

Xhtml_samp_typeDBs arrays xhtml_samp_typeDBs swagger:response xhtml_samp_typeDBsResponse.

Xhtml_span_typeDBs arrays xhtml_span_typeDBs swagger:response xhtml_span_typeDBsResponse.

Xhtml_strong_typeDBs arrays xhtml_strong_typeDBs swagger:response xhtml_strong_typeDBsResponse.

Xhtml_table_typeDBs arrays xhtml_table_typeDBs swagger:response xhtml_table_typeDBsResponse.

Xhtml_tbody_typeDBs arrays xhtml_tbody_typeDBs swagger:response xhtml_tbody_typeDBsResponse.

Xhtml_td_typeDBs arrays xhtml_td_typeDBs swagger:response xhtml_td_typeDBsResponse.

Xhtml_tfoot_typeDBs arrays xhtml_tfoot_typeDBs swagger:response xhtml_tfoot_typeDBsResponse.

Xhtml_th_typeDBs arrays xhtml_th_typeDBs swagger:response xhtml_th_typeDBsResponse.

Xhtml_thead_typeDBs arrays xhtml_thead_typeDBs swagger:response xhtml_thead_typeDBsResponse.

Xhtml_tr_typeDBs arrays xhtml_tr_typeDBs swagger:response xhtml_tr_typeDBsResponse.

Xhtml_ul_typeDBs arrays xhtml_ul_typeDBs swagger:response xhtml_ul_typeDBsResponse.

Xhtml_var_typeDBs arrays xhtml_var_typeDBs swagger:response xhtml_var_typeDBsResponse.