5 SODA Collection Configuration Using Custom Metadata

SODA collections are highly configurable. You can customize collection metadata, to obtain different behavior from that provided by default.

Note:

You can customize collection metadata to obtain different behavior from that provided by default. However, changing some components requires familiarity with Oracle Database concepts, such as SQL data types. Oracle recommends that you do not change such components unless you have a compelling reason. Because SODA collections are implemented on top of Oracle Database tables (or views), many collection configuration components are related to the underlying table configuration.

For example, if you change the content column type from the default value to VARCHAR2, then you must understand the implications: content size for VARCHAR2 is limited to 32K bytes, character-set conversion can take place, and so on.

• Getting the Metadata of an Existing Collection
  You use a GET catalog operation to get all of the metadata for a collection, as a JSON document.
• Creating a Collection That Has Custom Metadata
  You use a PUT collection operation to create a document collection that has custom metadata. You provide the metadata in the request body.

See Also:

• Overview of SODA Document Collections in Oracle Database Introduction to Simple Oracle Document Access (SODA) for general information about SODA document collections and their metadata

• SODA Collection Metadata Components (Reference) in Oracle Database Introduction to Simple Oracle Document Access (SODA) for reference information about collection metadata components