Package jakarta.nosql.document

This package contains all objects to use a Document Collection.

See: Description

Interface Summary

Interface	Description
DeleteQueryConverter	A converter that converts DeleteQuery to DocumentDeleteQueryParams
Document	A Document Collection Entity unit, it is a tuple (pair) that consists of a key-value pair, where the key is mapped to a value.
Document.DocumentProvider	A provider of Document where it will create from two parameters: The first one is the name of column The second one is the information of column
DocumentCollectionManager	Interface used to interact with the persistence context to DocumentEntity The DocumentCollectionManager API is used to create and remove persistent DocumentEntity instances, to select entities by their primary key, and to select over entities.
DocumentCollectionManagerFactory	DocumentCollectionManager factory.
DocumentCondition	An unit condition to run a document collection select
DocumentCondition.DocumentConditionProvider	A provider of DocumentCondition where it will create from two parameters: The first one is Document The second one is the Condition
DocumentConfiguration	The Jakarta NoSQL communication configuration to create a DocumentCollectionManagerFactory
DocumentDeleteQuery	A unit that has the columnFamily and condition to delete from conditions This instance will be used on:
DocumentDeleteQuery.DocumentDelete	The initial element in the Document delete query
DocumentDeleteQuery.DocumentDeleteFrom	The Document Delete Query
DocumentDeleteQuery.DocumentDeleteNameCondition	The base to delete name condition
DocumentDeleteQuery.DocumentDeleteNotCondition	The document not condition
DocumentDeleteQuery.DocumentDeleteProvider	A provider class of DocumentDeleteQuery.DocumentDelete
DocumentDeleteQuery.DocumentDeleteQueryBuild	The last step to the build of DocumentDeleteQuery.
DocumentDeleteQuery.DocumentDeleteWhere	The Document Where whose define the condition in the delete query.
DocumentDeleteQueryParams	The result of DocumentDeleteQueryParams that has DocumentDeleteQuery and Params.
DocumentEntity	A document-oriented database, or document store, is a computer program designed for storing, retrieving, and managing document-oriented information, also known as semi-structured data.
DocumentEntity.DocumentEntityProvider	A provider of DocumentEntity where it will return from the document entity name.
DocumentObserverParser	An observer to a parser; this observer allows checking both the name of an entity and the fields.
DocumentPreparedStatement	An object that represents a precompiled Query statement.
DocumentQuery	Class that contains information to do a select to DocumentCollectionManager
DocumentQuery.DocumentFrom	The DocumentFrom Query
DocumentQuery.DocumentLimit	The Document Order whose define the the maximum number of results to retrieve.
DocumentQuery.DocumentNameCondition	The base to name condition
DocumentQuery.DocumentNameOrder	The Column name order to the builder
DocumentQuery.DocumentNotCondition	The column not condition
DocumentQuery.DocumentOrder	The Document Order whose define the sort in the query.
DocumentQuery.DocumentQueryBuild	The last step to the build of DocumentQuery.
DocumentQuery.DocumentSelect	The initial element in the Document query
DocumentQuery.DocumentSelectProvider	A provider class of DocumentQuery.DocumentSelect
DocumentQuery.DocumentSkip	The Document Order whose define the position of the first result to retrieve.
DocumentQuery.DocumentWhere	The Document Where whose define the condition in the query.
DocumentQueryParams	The result of SelectQueryConverter that has DocumentQuery and Params.
DocumentQueryParser	A query parser to document database type, this class will convert a String to an operation in DocumentCollectionManager.
SelectQueryConverter	A converter that converts SelectQuery to DocumentQueryParams

Class Summary

Class	Description
Documents	This class has utilitarian class to Document

Package jakarta.nosql.document Description

This package contains all objects to use a Document Collection. This API gonna focus in domain, in other words, ubiquitous language. A document-oriented database, or document store, is a computer program designed for storing, retrieving, and managing document-oriented information, also known as semi-structured data. Document-oriented databases are one of the main categories of NoSQL databases, and the popularity of the term "document-oriented database" has grown with the use of the term NoSQL itself. XML databases are a subclass of document-oriented databases that are optimized to work with XML documents. Graph databases are similar, but add another layer, the relationship, which allows them to link documents for rapid traversal. Document-oriented databases are inherently a subclass of the key-value store, another NoSQL database concept. The difference lies in the way the data is processed; in a key-value store the data is considered to be inherently opaque to the database, whereas a document-oriented system relies on internal structure in the document in order to extract metadata that the database engine uses for further optimization. Although the difference is often moot due to tools in the systems, conceptually the document-store is designed to offer a richer experience with modern programming techniques. Document databases contrast strongly with the traditional relational database (RDB). Relational databases generally store data in separate tables that are defined by the programmer, and a single object may be spread across several tables. Document databases store all information for a given object in a single instance in the database, and every stored object can be different from every other. This makes mapping objects into the database a simple task, normally eliminating anything similar to an object-relational mapping. This makes document stores attractive for programming web applications, which are subject to continual change in place, and where speed of deployment is an important issue.