The most important task fulfilled by this instance is that it hides
different naming restrictions from you, which are caused by server-side
or client side specialities.
For instance, it can validate names against
the characters allowed in the object names of a connection. Also, it
relieves you from caring whether a database supports queries in a SELECT
statment's FROM
part (known as "queries in queries"). In such
databases, query and table names share a common namespace, thus they must be
unique. Using this interface, you can easily ensure this uniqueness.
All of the functionality present in this interface depends on a connection,
thus it entry point for obtaining it is a ::com::sun::star::sdb::Connection
service.
The component itself does not have life-time control mechanimns, i.e. you
cannot explicitly dispose it (::com::sun::star::lang::XComponent::dispose),
and you cannot be notified when it dies.
However, if your try to access any of its methods or attributes, after the
connection which was used to create it was closed, a ::com::sun::star::lang::DisposedException
will be thrown.