Abstract: Embodiments include methods, systems and computer program products method for editing and correcting structural metadata associated a binary large object (BLOB). The computer-implemented method includes obtaining, using a processor, at least a portion of structural metadata associated with the BLOB. The processor converts one or more fields associated with the at least a portion of structural metadata and determines that the one or more fields generated one or more errors or null values. The processor provides an interface, wherein the interface is used to cause a first movement or edit the one or more fields. The processor determines that the first movement or edit of the one or more fields fixes the one or more errors or null values and provides an indication that the first movement or edit of the one or more fields has or has not fixed the one or more errors or null values.

Abstract: Provided are techniques for interpreting invalid data that is a portion of a data set as valid data. A request is received to convert data from a first format to a second format for an application, wherein the data is a portion of a data set. It is determined that the data is invalid, wherein the invalid data cannot be processed by the application in the first format. It is determined whether the invalid data is to be interpreted as valid based on a flag. In response to determining that the invalid data is to be interpreted as valid, setting the invalid data to a new value in the second format that can be processed by the application.

Abstract: Provided are techniques for interpreting invalid data that is a portion of a data set as valid data. A request is received to convert data from a first format to a second format for an application, wherein the data is a portion of a data set. It is determined that the data is invalid, wherein the invalid data cannot be processed by the application in the first format. It is determined whether the invalid data is to be interpreted as valid based on a flag. In response to determining that the invalid data is to be interpreted as valid, setting the invalid data to a new value in the second format that can be processed by the application.

Abstract: Managing data conversion for user-defined data types within a DBMS. A custom data type definition and one or more converters are stored within a database management system. Each converter can convert instances of the custom data type between a binary format and a programming language format. The database management system receives a request for a custom data type instance in a specified programming language format. A converter among the one or more converters converts the custom data type instance expressed in the binary format into a custom data type instance expressed in the specified programming language format, using a custom data type definition from the database management system. The request is responded to with the converted custom data type instance in the specified programming language format.

Abstract: Embodiments include methods, systems and computer program products method for editing and correcting structural metadata associated a binary large object (BLOB). The computer-implemented method includes obtaining, using a processor, at least a portion of structural metadata associated with the BLOB. The processor converts one or more fields associated with the at least a portion of structural metadata and determines that the one or more fields generated one or more errors or null values. The processor provides an interface, wherein the interface is used to cause a first movement or edit the one or more fields. The processor determines that the first movement or edit of the one or more fields fixes the one or more errors or null values and provides an indication that the first movement or edit of the one or more fields has or has not fixed the one or more errors or null values.

Abstract: Provided are techniques for interpreting invalid data that is a portion of a data set as valid data. A request is received to convert data from a first format to a second format for an application, wherein the data is a portion of a data set. It is determined that the data is invalid, wherein the invalid data cannot be processed by the application in the first format. It is determined whether the invalid data is to be interpreted as valid based on a flag. In response to determining that the invalid data is to be interpreted as valid, setting the invalid data to a new value in the second format that can be processed by the application.

Abstract: Provided are techniques for interpreting invalid data that is a portion of a data set as valid data. A request is received to convert data from a first format to a second format for an application, wherein the data is a portion of a data set. It is determined that the data is invalid, wherein the invalid data cannot be processed by the application in the first format. It is determined whether the invalid data is to be interpreted as valid based on a flag. In response to determining that the invalid data is to be interpreted as valid, setting the invalid data to a new value in the second format that can be processed by the application.

Abstract: Managing data conversion for user-defined data types within a DBMS. A custom data type definition and one or more converters are stored within a database management system. Each converter can convert instances of the custom data type between a binary format and a programming language format. The database management system receives a request for a custom data type instance in a specified programming language format. A converter among the one or more converters converts the custom data type instance expressed in the binary format into a custom data type instance expressed in the specified programming language format, using a custom data type definition from the database management system. The request is responded to with the converted custom data type instance in the specified programming language format.

Abstract: Managing data conversion for user-defined data types within a DBMS. A custom data type definition and one or more converters are stored within a database management system. Each converter can convert instances of the custom data type between a binary format and a programming language format. The database management system receives a request for a custom data type instance in a specified programming language format. A converter among the one or more converters converts the custom data type instance expressed in the binary format into a custom data type instance expressed in the specified programming language format, using a custom data type definition from the database management system. The request is responded to with the converted custom data type instance in the specified programming language format.

Abstract: The capturing of rich database metadata includes: capturing partitioned column metadata of a database as mappings defined by a plurality of constraint statements; defining non-standard user-defined types of the database according to a schema; defining physical representations of columns of the database according to the schema; and storing the defined mappings, the defined user-defined types, and the defined physical representations of columns to a catalog of the database. Application enumerated data values in the database may also be defined according to the XML schema and stored to the catalog of the database. In this manner, the database management system may manage application constraints, user-defined types, and physical representations of data for applications referencing the same database using the metadata information stored in the catalog of the database.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: Provided are techniques for processing structured content within Large Object (LOB) data that is stored in a column of a database table. Structural metadata describing structures that each define a different format of the structured content is stored. A request for data in the database table is received. The structural metadata is used to create an empty result set with columns defined by at least two of the structures. For each row of data in the database table that includes LOB data, control data is used to identify one of the structures to be applied to the structured content within the LOB data stored in that row of data, and the structured content within the LOB data in that row of data is mapped to the columns in the result set based on the identified one of the structures. The result set is returned.

Abstract: The capturing of rich database metadata includes: capturing partitioned column metadata of a database as mappings defined by a plurality of constraint statements; defining non-standard user-defined types of the database according to a schema; defining physical representations of columns of the database according to the schema; and storing the defined mappings, the defined user-defined types, and the defined physical representations of columns to a catalog of the database. Application enumerated data values in the database may also be defined according to the XML schema and stored to the catalog of the database. In this manner, the database management system may manage application constraints, user-defined types, and physical representations of data for applications referencing the same database using the metadata information stored in the catalog of the database.

Abstract: The apparatus and system are provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: An apparatus, system, and method are provided for defining a metadata schema to facilitate passing data between an XML document and a hierarchical database. The invention includes a database accessor, a document accessor, and an association module. The database accessor accesses a database schema indicative of database field names and a hierarchical structure for a hierarchical database. The document accessor accesses a document schema that defines the hierarchical structure, content data syntax, and semantics of valid, well-formed, XML documents that can be passed into and out of the hierarchical database. The document schema also includes at least one XML element name that maps to a corresponding database field name in the database schema. The association module associates the database schema and the document schema to provide a metadata schema that enables data to be passed between an XML document and the hierarchical database.

Abstract: A method, computer program product, and system for making standard stream data accessible that would otherwise be lost in applications programs. Information placed on a standard stream, such as System.err or System.out in the Java development environment, can be lost during normal operation of the program (e.g., when not started from a system console or within an Integrated Development Environment (IDE)). A new stream is created and the standard stream is redirected to the new stream. Once data placed on the standard stream is available on the new stream it can be manipulated as desired and made available through a console or by placing the information into a file.