New! View global litigation for patent families

US6381600B1 - Exporting and importing of data in object-relational databases - Google Patents

Exporting and importing of data in object-relational databases Download PDF

Info

Publication number
US6381600B1
US6381600B1 US09404436 US40443699A US6381600B1 US 6381600 B1 US6381600 B1 US 6381600B1 US 09404436 US09404436 US 09404436 US 40443699 A US40443699 A US 40443699A US 6381600 B1 US6381600 B1 US 6381600B1
Authority
US
Grant status
Grant
Patent type
Prior art keywords
data
table
type
file
transfer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US09404436
Inventor
Leo Tat Man Lau
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Grant date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRICAL DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30286Information retrieval; Database structures therefor ; File system structures therefor in structured data stores
    • G06F17/30587Details of specialised database models
    • G06F17/30595Relational databases
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99932Access augmentation or optimizing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • Y10S707/99934Query formulation, input preparation, or translation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • Y10S707/99936Pattern matching access
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99937Sorting
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99942Manipulating data structure, e.g. compression, compaction, compilation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99943Generating database or data structure, e.g. via user interface
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing

Abstract

A computer system for transferring data from an object relational database to another such database. The data in the source database having a table type hierarchy of data tables. The system transforming data from the source database to a flat file format data transfer file using a defined tree traversal order. The columns and subcolumns of the data transfer file corresponding to types and attributes from the source database type hierarchy. The data transfer file having a type identifier column corresponding to a type in the table type hierarchy. The system permitting the inputting of the data from the data transfer file to a target database having a table type hierarchy corresponding to the table type hierarchy of the source database.

Description

FIELD OF THE INVENTION

The present invention is directed to an improvement in computing systems and in particular to computer systems which provide for the exporting and importing of data in object-relational databases.

BACKGROUND OF THE INVENTION

Computer systems for the storage and retrieval of data typically include a mechanism for the transfer of data from one system or database to another. Where data is stored in accordance with a relational model, the data will typically be exchanged between one database management system (DBMS) and another or between databases in the same DBMS, by way of one number of predefined flat file formats which correspond to tabular representations of the data. Examples of such file formats are ASC or DEL formats (non-delimited and delimited ASCII representations used in the DB2™ system), the PC IXF file format (a binary representation used in the DB2™ system) and the WSF file format (a format corresponding to a Lotus™ spreadsheet representation of data). In object-relational databases, a table in the database is modelled as a class of objects. A user of an object-relational database may define table hierarchies by extending a supertype which defines a table in the database with additional attributes to define subtypes which are in turn used for table definition in the database. The user-defined hierarchy of types defines a table hierarchy which may be populated with data in accordance with the needs of a user. This table hierarchy may be represented as a tree-structure in which the nodes are type definitions corresponding to tables in the database. Once a user has created a database having a user-defined table hierarchy in an object-relational DBMS a file format reflecting the table hierarchy must be used to move the data a new system or database. Data in a user-defined object-relational database table hierarchy cannot be directly exported (i.e. copied without a mapping or transformation step) from one DBMS and imported into another DBMS in the flat file formats used for non-object oriented relational databases.

Prior art systems contain features to permit the translation of hierarchical data into relational models. For example, U.S. Pat. No. 5,201,046 to Goldberg dated Apr. 6, 1993 discloses a DBMS which stores, retrieves and manipulates directed graph data structures in a relational database. Similarly, U.S. Pat. No. 5,799,310 to Anderson dated Aug. 25, 1998 describes relational extenders for handling complex data types. In U.S. Pat. No. 5,295,256 to Bapat dated Mar. 15, 1994, a translator for translating instances of objects in an object oriented programming environment into a relational database schema is described.

Such prior art systems, do not consider the translation of data from an object-relational database hierarchy to a standard flat file data exchange file format for transfer to a second object-relational database. Rather such systems extend relational models by defining new types within relational database columns, as in Anderson and Goldberg, or use multiple tables to persistently store instances of run-time objects used in an object-oriented programming language, as in Bapat. These prior art approaches map the hierarchical data into SQL schemas. It is therefore desirable to have a computer system which includes the capacity to export object-relational hierarchical data in a pre-defined flat file format to permit exchange to a second object-relational database.

SUMMARY OF THE INVENTION

According to one aspect of the present invention, there is provided an improved system for manipulating data in object-relational databases.

According to another aspect of the present invention, there is provided a computer system for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the system comprising, means for transforming data from the source database into a flat file data transfer file, comprising rows and columns, the means for transforming the source database comprising means for traversing the tree structure of the table type hierarchy using a tree traversal order, means for defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database, the means for defining the columns further comprising means for defining subcolumns corresponding to attributes defined in a respective type definition for a given column, the means for defining the columns further comprising means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order, the means for transforming data from the source database into the data transfer file further comprising means for copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.

According to another aspect of the present invention, there is provided the above computer system with input means for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input means comprising means for copying each row of data in the data transfer file to a target table in the target database, the target table being identified by the type identifier column value for the row of data in the data transfer file, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.

According to another aspect of the present invention, there is provided the above computer system in which the tree traversal order is user-definable and is constrained to be a pre-order, depth-first traversal and in which the default tree traversal order is a pre-order depth-first traversal with a sibling selection based on creation time for the type.

According to another aspect of the present invention, there is provided the above computer system in which characteristics defining the table type hierarchy for the source database are stored in the data transfer file and in which the characteristics defining the table type hierarchy for the source database comprise a traverse order table and a type identifier control table.

According to another aspect of the present invention, there is provided the above computer system in which hierarchy characteristics defining the table type hierarchy for the source database are stored in the data transfer file and which further comprises means for creating the table type hierarchy for the target database from the hierarchy characteristics.

According to another aspect of the present invention, there is provided the above computer system in which the input means further comprises means for accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and means for inputting only the specified columns of data from the data transfer file to the target database.

According to another aspect of the present invention, there is provided a computer program product for use with a computer comprising a central processing unit and random access memory, said computer program product comprising a computer usable medium having computer readable code means embodied in said medium for implementing a system as described above.

According to another aspect of the present invention, there is provided a method for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the method comprising the steps of

transforming data from the source database into a flat file data transfer file, comprising rows and columns, step of transforming the source database comprising the further steps of traversing the tree structure of the table type hierarchy using a tree traversal order,

defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database,

defining subcolumns corresponding to attributes defined in a respective type definition for a given column,

defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order,

copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.

According to another aspect of the present invention, there is provided the above method further comprising input steps for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input steps comprising copying each row of data in the data transfer file to a target table in the target database, the target table being identified by the type identifier column value for the row of data in the data transfer file, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.

According to another aspect of the present invention, there is provided a computer program product tangibly embodying a program of instructions executable by a computer to perform the method steps described above.

Advantages of the present invention include a system which provides the ability to transfer object relational data from one database to another using a defined flat file format data transfer file.

BRIEF DESCRIPTION OF THE DRAWINGS

The preferred embodiment of the invention is shown in the drawings, wherein:

FIG. 1 is a schematic block diagram showing the high level representation of the data flow in the preferred embodiment of the invention.

FIG. 2 is a tree diagram showing an example table hierarchy of types in an object relational database, the data for which is capable of being exported in accordance with the preferred embodiment of the invention.

In the drawings, the preferred embodiment of the invention is illustrated by way of example. It is to be expressly understood that the description and drawings are only for the purpose of illustration and as an aid to understanding, and are not intended as a definition of the limits of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The export and import of data in accordance with the preferred embodiment is shown in the schematic block diagram of FIG. 1. Source DBMS 10 contains source data 12 in an object-relational database, which data may be exported. Source data 12, in the example used to illustrate the preferred embodiment, has a set of defined types which make up a table hierarchy. Export transformation step 14 is shown with source data 12 as input and data transfer file 16 as output In accordance with the preferred embodiment of the invention, export transformation step 14 is shown as part of source DBMS 10. It will be understood by those skilled in the art that export transformation step 14 may be carried out by a process or module independent of source DBMS 10, or may be included (as in the preferred embodiment) as part of the commands of DBMS 10.

The import side of the system of the preferred embodiment is shown with reference to target DBMS 18. Target DBMS contains target data 20. In accordance with the preferred embodiment of the invention, the data in data transfer file 16 is imported by import transformation step 22, and the resulting data is stored in the hierarchical object-relational format of target data 20, which structure corresponds to all, or part of, the hierarchical structure of source data 12.

As may be seen from this high level description, in the preferred embodiment of the invention, object-relational DBMSs, shown in FIG. 1 as source DBMS 10 and target DBMS 18, are able to transfer data using the format of data transfer file 16. In the preferred embodiment, as described below, source data 12 and target data 20 have corresponding hierarchical object relational type definitions, while data transfer file 16 is a flat file of the type used for data transfer in prior art relational databases. It will be appreciated that the system of the preferred embodiment may also be used to transfer data from one database to another within the same DBMS, by way of the known format of data transfer file 16.

Turning to FIG. 2, a tree diagram is shown for an object-relational database reflecting an example hierarchy of types which define tables in the database. In FIG. 2 the root node of the tree is the type Person 30. Type Person 30 in the example of FIG. 2 is defined to have attributes as set out below. Type Person 30 has subtypes which are shown as nodes Student 32, Employee 34, and Owner 36. Each level in the tree structure of FIG. 2 contains nodes representing sub-types of the node in the previous level in the tree. As is shown in FIG. 2, Graduate 38 is a subtype of Student 32. Similarly, the types Developer 40 and Tester 42 are subtypes of the type Employee 34. The last node, type StaffDeveloper 44 is a subtype of type Developer 40.

The definitions of the attributes found in each type shown in the example of FIG. 2 are as follows:

Person: Name char (30), Age int

Student: StudentNum int

Graduate: ThesisTopic char (30)

Employee: Salary int

Developer: LineItem char (30)

Tester: TeamLeader char (30)

StaffDeveloper: Component char (30)

Owner: BusinessAddr char (30)

As is apparent to those skilled in the art, the sub-types set out in FIG. 2, the attributes for which are shown above, inherit the attributes of their parent types.

For the example table hierarchy set out in FIG. 2 and described above, the export data transformation of the preferred embodiment (shown as export transformation 14 in FIG. 1) will traverse the tree of the hierarchy to create a flat file corresponding to data transfer file 16 shown in FIG. 1. Data transfer file 16 of the preferred embodiment is capable of representing the data of the data hierarchy defined by the user in source DBMS 10. The user defines which portion of the data in source data 12 is to be exported and data transfer file 16 will be generated by export transformation 14 by the traversal of the subtree of the tree hierarchy corresponding to the data defined to be exported. In the example tree hierarchy of FIG. 2, the portion to be exported is shown in the defined subtree 46.

According to the preferred embodiment of the invention, the traversal of the types in the table definition hierarchy may be carried out in one of several ways. The traversal order of the tree structure of source data 12 defines the columns of data transfer file 16.

The system of the preferred embodiment defaults to a depth-first pre-order tree traversal to generate the columns for data transfer file 16. In this traversal order, child nodes in the tree are traversed in the order in which the nodes where created (the first created type is traversed first). Alternatively, the user may specify a particular order for the traversal of the nodes in the table hierarchy tree. The user-defined tree traversal ordering is constrained to be a depth-first pre-order traverse.

For a user-specified traverse order, the system of the preferred embodiment requires that there be:

An identical definition of subtables in both the source and the target databases;

An identical hierarchical relationship among the subtables in both the source and target databases; and

1. An identical traverse order in both the export and import steps.

There are two alternative approaches for this user-specified traversal: the system of the preferred embodiment may embed information about the traversal order in data transfer file 16, or the user may elect not to embed the information in the file but to specify the traversal order at both export transformation step 14 and import transformation step 22. In the system of the preferred embodiment, the former approach, in which a record of all relevant types, their definitions and relevant tables is created in export transformation step 14, is available for PC/IXF format data transfer file 16. However, the decision to permit this information to be transferred for certain formats of data transfer file 16 is an implementation decision which will vary from system to system, depending on the requirements of users and details of the systems and file formats.

Where the user specifies the traversal order, the system of the preferred embodiment requires that the traversal be in pre-order. The pre-order traversal is one in which each branch in the hierarchy must be traversed to the bottom before a new branch is traversed.

The table corresponding to data transfer file 16 which is created by the system of the preferred embodiment for two records of sample data in the table hierarchy as shown in FIG. 2 is set out in Table 1, below:

TABLE 1
Em-
Type Person ployee Developer StaffDeveloper Tester
ID Name Age Salary LineItem Component TeamLeader
3 John 22 30,000 Crash Nil Nil
Recovery
4 Sam 35 50,000 Load Load Nil

The system of the preferred embodiment, using the default depth-first pre-order traversal of the tree structure shown in FIG. 2 for subtree 46, will notionally generate a traverse order table as shown in Table 2, below (such a table is not expressly created in the system of the preferred embodiment):

TABLE 2
Traverse
Node Order
Person 1
Employee 2
Developer 3
StaffDeveloper 4
Tester 5

As is shown in Table 1, a column in the table is created for each node traversed in subtree 46. For each attribute defined in the node, a subcolumn is created. Thus for the node for type Developer 40, there is a LineItem column added to Table 1. The single table of data file transfer file 16 is therefore able to store data values for records in the different typed tables found in the table hierarchy of FIG. 2 in a flat file configuration.

The format of the table shown in Table 1 also includes a column for TypeID. This is a value derived from the traverse order of the tree traversal used to create Table 1. It represents the table from which a row in Table 1 is copied. The TypeID also corresponds to the values in Table 2, if such a table is maintained (the existence of Table 2 in the system of the preferred embodiment depends on the user's selection of traversal method).

The TypeID is used by import transformation step 22 to recreate the object-relational data in target data 20. In the example of Table 1, the TypeID 3 for the first row in the table specifies that the node in target data 20 to which the first row of data will be written is in Developer node 40 in the table hierarchy of FIG. 2. Similarly, TypeID 4 in the second row of data in Table 1 indicates that the data in that row is from StaffDeveloper node 44 in FIG. 2.

As the above indicates, the traversal order used to generate data transfer file 16 is used to determine how the data in source data 12 is written to the flat file, and specifies how data in data transfer file 16 is written to target data 20. Thus the traverse order defines the mapping between columns in data transfer file 16 and attributes in the tables in source data 12 and target data 20. As set out above, the traversal order may be specified by default, may be expressly stored in data transfer file 16, or may be input by the user as part of import transformation step 22.

In accordance with the preferred embodiment of the invention, where the traversal order information is stored in data transfer file 16, TypeID control information is stored as is shown in Table 3, below:

TABLE 3
Name StartingCol EndingCol Parent
Person 1 2 −1  
Employee 3 3 0
Developer 4 4 1
StaffDeveloper 5 5 2
Tester 6 6 1

The information in Table 3 is used to recreate the hierarchical tree structure for the object relational data in Target DBMS 18. The columns StartingCol and EndingCol indicate where data transfer file 16 the attributes for the node specified in the Name column, may be found. Parent column in Table 3 is a pointer into the table itself (with zero-based indexing, and −1 representing a null pointer).

In the system of the preferred embodiment, the information found in the examples of Table 2 and Table 3 may be stored in data transfer file 16. In such a case, the system of the preferred embodiment provides that import transformation step 22 may create the table hierarchy specified by data transfer file 16. In the preferred embodiment, where the above information is not available in data transfer file 16, import transformation step 22 relies on the table hierarchy for the data to be pre-defined by the user in target data 20.

As may be seen by the above example, in the system of the preferred embodiment, the object relational data in a table hierarchy such as that shown in FIG. 2 may be written to data transfer file 16 in a flat file format as shown in Table 1. This format is consistent with other flat file formats for data exchanged between relational database systems and does not require special data structures for each defined table hierarchy. The same flat file format is available for all table hierarchies. Import transformation step 22 makes use of the data in the flat file format of data transfer file 16. Where necessary, tree traversal information shown in the examples of Table 2 and Table 3 is made available and used by import transformation step 22 in the copying of data into the defined table hierarchy in Target DBMS 18. The TypeID information found in data transfer file 16 specifies into which table in Target Data 20 the data in data transfer file 16 is to be copied. In import transformation 22, the preferred embodiment provides that the user may specify an attributes list at the end of each subtable name to restrict the attributes that are moved to target data 20. If no attributes list is used, all the columns in each subtable are moved. Import transformation 22 also permits the user to specify which columns from the data transfer file are to be imported into target data 20. In the system of the preferred embodiment, the file type of data transfer file 16 will determine how the columns are designated (by start and end column numbers for ASC files, by names of columns for IXF files, and by column number for the IDF or DEL files). In the system of the preferred embodiment, import transformation step 22 involves the copying of data in data transfer file 16 to target data 20. As described above, import transformation step 22 may create the type hierarchy for the tables of target data 20, when export transformation step 14 has stored the information detailing the type hierarchy in data transfer file 16. Alternatively, the table definition type hierarchy for target data 20 will be user-defined to accept the data from data transfer file 16 which is to be input in to target DBMS 18. Import transformation step 22 reads records from the table of data transfer file 16 and copies the records to the table in target data 20 as indicated by the TypeID value for each record (from the TypeID column in the flat file of data transfer file 16). In this way, the data which originated in source data 12 will be copied into the appropriately corresponding hierarchy in target data 20. The traversal order used to define the columns of data transfer file 16 will be used to determine the column to attribute mapping when copying data to target data 20 from data transfer file 16. In this way the data transfer between the two hierarchical object relational databases is achieved using the flat file of data transfer file 16. Although a preferred embodiment of the present invention has been described here in detail, it will be appreciated by those skilled in the art, that variations may be made thereto, without departing from the spirit of the invention or the scope of the appended claims.

Claims (63)

The embodiments of the invention in which an exclusive property or privilege is claimed are defined as follows:
1. A computer system for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the system comprising,
means for transforming data from the source database into a flat file data transfer file, comprising rows and columns, the means for transforming the source database comprising
means for traversing the tree structure of the table type hierarchy using a tree traversal order,
means for defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database,
the means for defining the columns further comprising means for defining subcolumns corresponding to attributes defined in a respective type definition for a given column,
the means for defining the columns further comprising means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order,
the means for transforming data from the source database into the data transfer file further comprising means for copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
2. The computer system of claim 1, further comprising input means for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input means comprising means for copying each row of data in the data transfer file to a target table in the target database, the target table being identified by the type identifier column value for the row of data in the data transfer file, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
3. The computer system of claim 1 in which the tree traversal order is user-definable and is constrained to be a pre-order, depth-first traversal.
4. The computer system of claim 1 in which the default tree traversal order is a pre-order, depth-first traversal in which sibling selection is based on creation time of the type for the node in the tree.
5. The computer system of claim of claim 1 in which characteristics defining the table type hierarchy for the source database are stored in the data transfer file.
6. The computer system of claim 5 in which the characteristics defining the table type hierarchy for the source database comprise a type identifier control table.
7. The computer system of claim 2 in which hierarchy characteristics defining the table type hierarchy for the source database are stored in the data transfer file and which further comprises means for creating the table type hierarchy for the target database from the hierarchy characteristics.
8. The computer system of claim 7 in which the hierarchy characteristics comprise a type identifier control table.
9. The computer system of claim 2 in which the input means further comprises means for accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and means for inputting only the specified columns of data from the data transfer file to the target database.
10. The computer system of claim 1 in which the data transfer file has a format selected from one of PC/IXF, worksheet, delimited ASCII and non-delimited ASCII, formats.
11. A computer program product for use with a computer comprising a central processing unit and random access memory, said computer program product comprising a computer usable medium having computer readable code means embodied in said medium for manipulating data in an object relational source, the source database having data tables and a defined table type hierarchy with an associate tree structure, said computer program product comprising:
computer readable program code means for causing a computer to transform data from the source database into a flat file data transfer file having rows and columns, comprising
means for traversing the tree structure of the table type hierarchy using a tree traversal order,
means for defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database,
the means for defining the columns further comprising means for defining subcolumns corresponding to attributes defined in a respective type definition for a given column,
the means for defining the columns further comprising means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order,
the computer readable program code means for causing a computer to transform data from the source database into the data transfer file further comprising means for copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
12. The computer program product of claim 11, further comprising input means for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input means comprising means for copying each row of data in the data transfer file to a target table in the target database, the target table being identified by the type identifier column value for the row of data in the data transfer file, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
13. A method for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the method comprising the steps of
transforming data from the source database into a flat file data transfer file, comprising rows and columns, step of transforming the source database comprising the further steps of
traversing the tree structure of the table type hierarchy using a tree traversal order,
defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database,
defining subcolumns corresponding to attributes defined in a respective type definition for a given column,
defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order,
copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
14. The method of claim 13, further comprising input steps for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input steps comprising copying each row of data in the data transfer file to a target table in the target database, the target table being identified by the type identifier column value for the row of data in the data transfer file, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
15. The method of claim 13 further comprising the step of accepting from the user a the tree traversal order definition and constraining the traversal order to be a depth-first, pre-order traversal.
16. The method of claim 13 further comprising the step of storing characteristics defining the table type hierarchy for the source database in the data transfer file.
17. The method of claim 16 in which the characteristics defining the table type hierarchy for the source database comprise a type identifier control table.
18. The method of claim 14 further comprising the step of storing hierarchy characteristics defining the table type hierarchy for the source database in the data transfer file and which further comprises the step of creating the table type hierarchy for the target database from the hierarchy characteristics.
19. The method of claim 18 in which the hierarchy characteristics comprise a type identifier control table.
20. The method of claim 14 in which the input step further comprises the step of accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and inputting only the specified columns of data from the data transfer file to the target database.
21. A computer program product tangibly embodying a program of instructions executable by a computer to perform the method steps of claim 13.
22. A computer program product tangibly embodying a program of instructions executable by a computer to perform the method steps of claim 14.
23. A computer program product tangibly embodying a program of instructions executable by a computer to perform the method steps of claim 19.
24. A computer system for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the system comprising,
means for transforming data from the source database into a flat file data transfer file, comprising rows and columns, the means for transforming the source database comprising
means for traversing the tree structure of the table type hierarchy using a tree traversal order, and
means for defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database.
25. The computer system of claim 24, wherein the means for defining the columns further comprises means for defining subcolumns corresponding to attributes defined in a respective type definition for a given column, and wherein the means for defining the columns further comprises means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order.
26. The computer system of claim 25, wherein the means for transforming data from the source database into the data transfer file further comprises means for copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
27. The computer system of claim 24, further comprising input means for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input means comprising means for copying each row of data in the data transfer file to a target table in the target database, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
28. The system of claim 27, wherein the means for defining the columns further comprises means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, wherein each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file, and wherein the target table is identified by the type identifier column value for the row of data in the data transfer file.
29. The computer system of claim 24 in which the tree traversal order is user-definable and is constrained to be a pre-order, depth-first traversal.
30. The computer system of claim 24 in which the default tree traversal order is a pre-order, depth-first traversal in which sibling selection is based on creation time of the type for the node in the tree.
31. The computer system of claim of claim 24 in which characteristics defining the table type hierarchy for the source database are stored in the data transfer file.
32. The computer system of claim 31 in which the characteristics defining the table type hierarchy for the source database comprise a type identifier control table.
33. The computer system of claim 27 in which hierarchy characteristics defining the table type hierarchy for the source database are stored in the data transfer file and which further comprises means for creating the table type hierarchy for the target database from the hierarchy characteristics.
34. The computer system of claim 33 in which the hierarchy characteristics comprise a type identifier control table.
35. The computer system of claim 27 in which the input means further comprises means for accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and means for inputting only the specified columns of data from the data transfer file to the target database.
36. The computer system of claim 24 in which the data transfer file has a format selected from one of PC/IXF, worksheet, delimited ASCII and non-delimited ASCII, formats.
37. A computer program product for use with a computer comprising a central processing unit and random access memory, said computer program product comprising a computer usable medium having computer readable code means embodied in said medium for manipulating data in an object relational source, the source database having data tables and a defined table type hierarchy with an associate tree structure, said computer program product comprising:
computer readable program code means for causing a computer to transform data from the source database into a flat file data transfer file having rows and columns, comprising
means for traversing the tree structure of the table type hierarchy using a tree traversal-order, and
means for defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database.
38. The computer program product of claim 37, wherein the means for defining the columns further comprise means for defining subcolumns corresponding to attributes defined in a respective type definition for a given column, and the means for defining the columns further comprise means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order.
39. The computer program product of claim 38, wherein the computer readable program code means for causing a computer to transform data from the source database into the data transfer file further comprises means for copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
40. The computer program product of claim 37, further comprising input means for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input means comprising means for copying each row of data in the data transfer file to a target table in the target database, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
41. The computer program product of claim 40, wherein the means for defining the columns further comprises means for defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, wherein each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file, and wherein the target table is identified by the type identifier column value for the row of data in the data transfer file.
42. A method for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the method comprising the steps of
transforming data from the source database into a flat file data transfer file, comprising rows and columns, step of transforming the source database comprising the further steps of
traversing the tree structure of the table type hierarchy using a tree traversal order, and
defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database.
43. The method of claim 42, further comprising the steps of:
defining subcolumns corresponding to attributes defined in a respective type definition for a given column, and
defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order.
44. The method of claim 43, further comprising the step of copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
45. The method of claim 42, further comprising input steps for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input steps comprising copying each row of data in the data transfer file to a target table in the target database, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
46. The method of claim 45, further comprising the step of:
defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order, wherein each row in the data transfer file has a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file, and wherein the target table is identified by the type identifier column value for the row of data in the data transfer file.
47. The method of claim 42 further comprising the step of accepting from the user a the tree traversal order definition and constraining the traversal order to be a depth-first, pre-order traversal.
48. The method of claim 42 further comprising the step of storing characteristics defining the table type hierarchy for the source database in the data transfer file.
49. The method of claim 48 in which the characteristics defining the table type hierarchy for the source database comprise a type identifier control table.
50. The method of claim 45 further comprising the step of storing hierarchy characteristics defining the table type hierarchy for the source database in the data transfer file and which further comprises the step of creating the table type hierarchy for the target database from the hierarchy characteristics.
51. The method of claim 50 in which the hierarchy characteristics comprise a type identifier control table.
52. The method of claim 45 in which the input step further comprises the step of accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and inputting only the specified columns of data from the data transfer file to the target database.
53. A computer program product tangibly embodying a program of instructions executable by a computer to perform a method for manipulating data in an object relational source database, the source database having data tables and a defined table type hierarchy with an associated tree structure, the method comprising the steps of
transforming data from the source database into a flat file data transfer file, comprising rows and columns, step of transforming the source database comprising the further steps of
traversing the tree structure of the table type hierarchy using a tree traversal order, and
defining the columns in the data transfer file to correspond to the type definitions in the table type hierarchy for the source database.
54. The method of claim 53, further comprising the steps of:
defining subcolumns corresponding to attributes defined in a respective type definition for a given column, and
defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order.
55. The method of claim 54, further comprising the step of copying rows of data from the tables in the source database into the data transfer file, each row in the data transfer file having a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file.
56. The method of claim 53, further comprising input steps for transforming data in the data transfer file to a target object relational database, the target object relational database having a table type hierarchy corresponding to the table type hierarchy of the source database, the input steps comprising copying each row of data in the data transfer file to a target table in the target database, the data for each column in the row of data in the data transfer file being copied to the column in the target table as defined by the tree traversal order.
57. The method of claim 56, further comprising the step of:
defining a type identifier column corresponding to a type identifier determined during the traversal of the tree structure, the type identifier column values corresponding to defined types in the table type hierarchy and determined by the tree traversal order, wherein each row in the data transfer file has a type identifier column value corresponding to the table in the table type hierarchy of the source database which is the source of the data in the row in the data transfer file, and wherein the target table is identified by the type identifier column value for the row of data in the data transfer file.
58. The method of claim 53 further comprising the step of accepting from the user a the tree traversal order definition and constraining the traversal order to be a depth-first, pre-order traversal.
59. The method of claim 53 further comprising the step of storing characteristics defining the table type hierarchy for the source database in the data transfer file.
60. The method of claim 59 in which the characteristics defining the table type hierarchy for the source database comprise a type identifier control table.
61. The method of claim 56 further comprising the step of storing hierarchy characteristics defining the table type hierarchy for the source database in the data transfer file and which further comprises the step of creating the table type hierarchy for the target database from the hierarchy characteristics.
62. The method of claim 61 in which the hierarchy characteristics comprise a type identifier control table.
63. The method of claim 56 in which the input step further comprises the step of accepting an attribute list from a user, the attribute list corresponding to specified columns in the data transfer file and inputting only the specified columns of data from the data transfer file to the target database.
US09404436 1999-09-22 1999-09-22 Exporting and importing of data in object-relational databases Active US6381600B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09404436 US6381600B1 (en) 1999-09-22 1999-09-22 Exporting and importing of data in object-relational databases

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09404436 US6381600B1 (en) 1999-09-22 1999-09-22 Exporting and importing of data in object-relational databases
US10095446 US6502098B2 (en) 1999-09-22 2002-03-13 Exporting and importing of data in object-relational databases

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10095446 Continuation US6502098B2 (en) 1999-09-22 2002-03-13 Exporting and importing of data in object-relational databases

Publications (1)

Publication Number Publication Date
US6381600B1 true US6381600B1 (en) 2002-04-30

Family

ID=23599595

Family Applications (2)

Application Number Title Priority Date Filing Date
US09404436 Active US6381600B1 (en) 1999-09-22 1999-09-22 Exporting and importing of data in object-relational databases
US10095446 Active US6502098B2 (en) 1999-09-22 2002-03-13 Exporting and importing of data in object-relational databases

Family Applications After (1)

Application Number Title Priority Date Filing Date
US10095446 Active US6502098B2 (en) 1999-09-22 2002-03-13 Exporting and importing of data in object-relational databases

Country Status (1)

Country Link
US (2) US6381600B1 (en)

Cited By (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020191033A1 (en) * 2001-06-15 2002-12-19 Scott Roberts Systems and methods for creating and displaying a user interface for displaying hierarchical data
US20020198897A1 (en) * 2001-06-21 2002-12-26 International Business Machines Corporation Method and system for transferring data between server systems
US20030105752A1 (en) * 2001-11-27 2003-06-05 General Electric Financial Assurance Holdings, Inc Method and system for performing processing data
US20030110179A1 (en) * 2001-12-10 2003-06-12 Oracle Corporation Database system having heterogeneous object types
US20040068513A1 (en) * 2002-10-02 2004-04-08 Carroll David B. System and method for organizing information
US20040083222A1 (en) * 2002-05-09 2004-04-29 Robert Pecherer Method of recursive objects for representing hierarchies in relational database systems
US6760019B1 (en) * 2000-06-01 2004-07-06 Sun Microsystems, Inc. Methods and apparatus for facilitating the sharing of computer graphics operations
US6791585B1 (en) * 2000-01-21 2004-09-14 International Business Machines Corporation Computer method and system for reconciling disparate data archival mediums
US20050055351A1 (en) * 2003-09-05 2005-03-10 Oracle International Corporation Apparatus and methods for transferring database objects into and out of database systems
US20050198617A1 (en) * 2004-03-04 2005-09-08 Vivcom, Inc. Graphically browsing schema documents described by XML schema
US20050257125A1 (en) * 2004-05-17 2005-11-17 Sap Aktiengesellschaft Methods and systems for importing source data
US20050262113A1 (en) * 2004-05-14 2005-11-24 Geeta Arora Interpreting remote objects at a local site
US20060074947A1 (en) * 2003-03-10 2006-04-06 Mazzagatti Jane C System and method for storing and accessing data in an interlocking trees datastore
US20060161581A1 (en) * 2001-08-31 2006-07-20 Bmc Software, Inc. Service desk data transfer interface
EP1686487A2 (en) * 2005-02-01 2006-08-02 Microsoft Corporation Mechanisms for transferring raw data from one data structure to another representing the same item
US20060280511A1 (en) * 2005-06-14 2006-12-14 Ryutaro Futami Optical receiver having bias circuit for avalanche photodiode with wide dynamic range
US20070038654A1 (en) * 2004-11-08 2007-02-15 Mazzagatti Jane C API to KStore interlocking trees datastore
US7213041B2 (en) 2004-10-05 2007-05-01 Unisys Corporation Saving and restoring an interlocking trees datastore
US20070162508A1 (en) * 2004-11-08 2007-07-12 Mazzagatti Jane C Updating information in an interlocking trees datastore
US20070214153A1 (en) * 2006-03-10 2007-09-13 Mazzagatti Jane C Method for processing an input particle stream for creating upper levels of KStore
US20070220070A1 (en) * 2006-03-20 2007-09-20 Mazzagatti Jane C Method for processing sensor data within a particle stream by a KStore
US20070220069A1 (en) * 2006-03-20 2007-09-20 Mazzagatti Jane C Method for processing an input particle stream for creating lower levels of a KStore
US20070233723A1 (en) * 2006-04-04 2007-10-04 Mazzagatti Jane C Method for determining a most probable K location
US7340471B2 (en) 2004-01-16 2008-03-04 Unisys Corporation Saving and restoring an interlocking trees datastore
US7348980B2 (en) 2004-11-08 2008-03-25 Unisys Corporation Method and apparatus for interface for graphic display of data from a Kstore
US7389301B1 (en) 2005-06-10 2008-06-17 Unisys Corporation Data aggregation user interface and analytic adapted for a KStore
US20080177870A1 (en) * 2006-12-22 2008-07-24 International Business Machines Corporation Selecting information for ad hoc exchange
US7409380B1 (en) 2005-04-07 2008-08-05 Unisys Corporation Facilitated reuse of K locations in a knowledge store
US7418445B1 (en) 2004-11-08 2008-08-26 Unisys Corporation Method for reducing the scope of the K node construction lock
US20080243876A1 (en) * 2007-03-30 2008-10-02 International Business Machines Corporation Creation of generic hierarchies
US20080275842A1 (en) * 2006-03-20 2008-11-06 Jane Campbell Mazzagatti Method for processing counts when an end node is encountered
US20080301162A1 (en) * 2007-05-31 2008-12-04 Bank Of America Corporation Data conversion environment
US7571182B1 (en) 2005-01-26 2009-08-04 Star Analytics, Inc. Emulation of a balanced hierarchy from a nonbalanced hierarchy
US7593923B1 (en) 2004-06-29 2009-09-22 Unisys Corporation Functional operations for accessing and/or building interlocking trees datastores to enable their use with applications software
US7676330B1 (en) 2006-05-16 2010-03-09 Unisys Corporation Method for processing a particle using a sensor structure
US7676477B1 (en) 2005-10-24 2010-03-09 Unisys Corporation Utilities for deriving values and information from within an interlocking trees data store
US7689571B1 (en) 2006-03-24 2010-03-30 Unisys Corporation Optimizing the size of an interlocking tree datastore structure for KStore
US7716241B1 (en) 2004-10-27 2010-05-11 Unisys Corporation Storing the repository origin of data inputs within a knowledge store
US20100145727A1 (en) * 2008-12-08 2010-06-10 Microsoft Corporation Interaction between healthcare software products
US7908240B1 (en) 2004-10-28 2011-03-15 Unisys Corporation Facilitated use of column and field data for field record universe in a knowledge store
WO2011074942A1 (en) * 2009-12-16 2011-06-23 Emanual System Sdn Bhd System and method of converting data from a multiple table structure into an edoc format
US20120089562A1 (en) * 2010-10-04 2012-04-12 Sempras Software, Inc. Methods and Apparatus for Integrated Management of Structured Data From Various Sources and Having Various Formats
US20120254235A1 (en) * 2001-07-18 2012-10-04 Tralee Software Pty. Ltd. Content transfer
US8516004B2 (en) 2003-09-19 2013-08-20 Unisys Corporation Method for processing K node count fields using an intensity variable
CN103412765A (en) * 2013-09-04 2013-11-27 广东全通教育股份有限公司 Method for realizing universality of data exporting interface
CN103455589A (en) * 2013-08-29 2013-12-18 中国农业银行股份有限公司 Product data migration method, device and system in product factory pattern
US20160353135A1 (en) * 2014-02-28 2016-12-01 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving signaling information in digital broadcast system
US9864764B2 (en) * 2014-08-29 2018-01-09 Accenture Global Solutions Limited Evolving data archives
US9934296B2 (en) * 2001-07-18 2018-04-03 Semantic Technologies Pty Ltd Content transfer

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7203945B2 (en) * 2001-08-16 2007-04-10 Sun Microsystems, Inc. Import/export utility and a method of processing data using the same
DE10249482A1 (en) * 2002-10-24 2004-05-13 Bayer Ag Project risk analysis method, by generating checklists, exporting data from hierarchical database to relational database and performing risk analysis by accessing relational database
US8538840B2 (en) * 2002-12-20 2013-09-17 Siebel Systems, Inc. Financial services data model
US7017112B2 (en) * 2003-02-28 2006-03-21 Microsoft Corporation Importing and exporting markup language data in a spreadsheet application document
US8392298B2 (en) * 2003-03-04 2013-03-05 Siebel Systems, Inc. Invoice adjustment data object for a common data object format
US8473399B2 (en) * 2003-03-04 2013-06-25 Siebel Systems, Inc. Invoice data object for a common data object format
US7313561B2 (en) * 2003-03-12 2007-12-25 Microsoft Corporation Model definition schema
US9704120B2 (en) * 2003-03-24 2017-07-11 Oracle International Corporation Inventory balance common object
US8510179B2 (en) * 2003-03-24 2013-08-13 Siebel Systems, Inc. Inventory transaction common object
US8489470B2 (en) * 2003-03-24 2013-07-16 Siebel Systems, Inc. Inventory location common object
US7904340B2 (en) * 2003-03-24 2011-03-08 Siebel Systems, Inc. Methods and computer-readable medium for defining a product model
US20070226037A1 (en) * 2003-03-25 2007-09-27 Shailendra Garg Modeling of opportunity data
US7509327B2 (en) * 2003-12-03 2009-03-24 Microsoft Corporation Business data migration using metadata
EP1569132B1 (en) * 2004-02-23 2012-07-04 Sap Ag Computer system and method of performing a database access
US20060074841A1 (en) * 2004-09-27 2006-04-06 Harikrishnan Sugumaran Method, system, and program for translating and interfacing between data pools and product information management (PIM) systems
WO2006037613A3 (en) * 2004-10-04 2006-08-24 Andy David Ben-Dyke Method and system for implementing an enhanced database
US8738891B1 (en) * 2004-11-15 2014-05-27 Nvidia Corporation Methods and systems for command acceleration in a video processor via translation of scalar instructions into vector instructions
US20060176496A1 (en) * 2005-02-04 2006-08-10 Leshek Fiedorowicz Extensible transformation framework
US20060242176A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of exposing business configuration dependencies
US20060241999A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of exposing a sequence of instructions into an object-oriented programming language
US20060282458A1 (en) * 2005-04-22 2006-12-14 Igor Tsyganskiy Methods and systems for merging business process configurations
US20060241961A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of optimizing legacy application layer control structure using refactoring
US7720879B2 (en) * 2005-04-22 2010-05-18 Sap Ag Methods of using an integrated development environment to configure business applications
US20060242177A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of exposing business application runtime exceptions at design time
US7958486B2 (en) 2005-04-22 2011-06-07 Sap Ag Methods and systems for data-focused debugging and tracing capabilities
US20060293935A1 (en) * 2005-04-22 2006-12-28 Igor Tsyganskiy Methods and systems for incrementally exposing business application errors using an integrated display
US8539003B2 (en) 2005-04-22 2013-09-17 Sap Ag Systems and methods for identifying problems of a business application in a customer support system
US20060242197A1 (en) 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of transforming application layer structure as objects
US7542980B2 (en) 2005-04-22 2009-06-02 Sap Ag Methods of comparing and merging business process configurations
US7702638B2 (en) * 2005-04-22 2010-04-20 Sap Ag Systems and methods for off-line modeling a business application
US20060242188A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of exposing a missing collection of application elements as deprecated
US20060242172A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Systems and methods for transforming logic entities of a business application into an object-oriented model
US20060242196A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of exposing application layer integrity as object oriented programming language elements
US20060242171A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Methods of using code-based case tools to verify application layer configurations
US20060242174A1 (en) * 2005-04-22 2006-10-26 Igor Tsyganskiy Systems and methods for using object-oriented tools to debug business applications
US20060293940A1 (en) * 2005-04-22 2006-12-28 Igor Tsyganskiy Methods and systems for applying intelligent filters and identifying life cycle events for data elements during business application debugging
US8935294B2 (en) * 2005-08-10 2015-01-13 Oracle International Corporation Minimizing computer resource usage when converting data types of a table column
US7752651B2 (en) * 2005-09-26 2010-07-06 Bea Systems Inc. System and method for propagating security information in a web portal system
US7730477B2 (en) * 2005-09-26 2010-06-01 Bea Systems Inc. System and method for propagation in a web portal system
US7853573B2 (en) * 2006-05-03 2010-12-14 Oracle International Corporation Efficient replication of XML data in a relational database management system
US7801856B2 (en) * 2006-08-09 2010-09-21 Oracle International Corporation Using XML for flexible replication of complex types
US7849108B1 (en) * 2007-03-13 2010-12-07 Fundriver, Inc. Methods and systems for establishing a database
US20080235041A1 (en) * 2007-03-21 2008-09-25 Cashdollar Jeffrey J Enterprise data management
US9569482B2 (en) * 2007-05-09 2017-02-14 Oracle International Corporation Transforming default values dynamically
US20090106128A1 (en) * 2007-10-19 2009-04-23 Oracle International Corporation Web Service Architecture for Product Selection and Dynamic Catalog Generation
US20110191304A1 (en) * 2010-01-29 2011-08-04 Software Ag, Inc. System and method for export and import of metadata located in metadata registries

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0231119A2 (en) * 1986-01-31 1987-08-05 Computer Associates International, Inc. Method and system for retrieval of stored graphs
US4894771A (en) * 1987-12-19 1990-01-16 Ricoh Company, Ltd. Data base management system extending structure
US5201046A (en) * 1990-06-22 1993-04-06 Xidak, Inc. Relational database management system and method for storing, retrieving and modifying directed graph data structures
JPH05225250A (en) * 1992-02-17 1993-09-03 Fujitsu Ltd Table coupling system for relational data base
BE1005836A6 (en) * 1993-10-05 1994-02-15 L & P Systems Ltd Improvements in the effectiveness of the data processing and related.
US5295256A (en) * 1990-12-14 1994-03-15 Racal-Datacom, Inc. Automatic storage of persistent objects in a relational schema
WO1994015310A1 (en) * 1992-12-22 1994-07-07 Roy Jack Bernard Assersohn Information storage and retrieval system
US5432942A (en) * 1993-06-10 1995-07-11 The United States Of America As Represented By The Secretary Of The Navy Data structure extraction, conversion and display tool
US5499358A (en) * 1993-12-10 1996-03-12 Novell, Inc. Method for storing a database in extended attributes of a file system
US5504886A (en) * 1993-07-02 1996-04-02 International Business Machines Corporation System and method for applying user supplied relation definitions to application files for a relational database
CA2151654A1 (en) * 1995-06-13 1996-12-14 William D. Devlin Graphical display method and apparatus
JPH0962547A (en) 1995-08-29 1997-03-07 Nec Software Ltd Data management system
US5764973A (en) * 1994-02-08 1998-06-09 Enterworks.Com, Inc. System for generating structured query language statements and integrating legacy systems
US5799310A (en) * 1995-05-01 1998-08-25 International Business Machines Corporation Relational database extenders for handling complex data types
US6208990B1 (en) * 1998-07-15 2001-03-27 Informatica Corporation Method and architecture for automated optimization of ETL throughput in data warehousing applications

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4852019A (en) * 1986-01-31 1989-07-25 Computer Associates International, Inc. Method and system for retrieval of stored graphs
EP0231119A2 (en) * 1986-01-31 1987-08-05 Computer Associates International, Inc. Method and system for retrieval of stored graphs
US4894771A (en) * 1987-12-19 1990-01-16 Ricoh Company, Ltd. Data base management system extending structure
US5201046A (en) * 1990-06-22 1993-04-06 Xidak, Inc. Relational database management system and method for storing, retrieving and modifying directed graph data structures
US5295256A (en) * 1990-12-14 1994-03-15 Racal-Datacom, Inc. Automatic storage of persistent objects in a relational schema
JPH05225250A (en) * 1992-02-17 1993-09-03 Fujitsu Ltd Table coupling system for relational data base
WO1994015310A1 (en) * 1992-12-22 1994-07-07 Roy Jack Bernard Assersohn Information storage and retrieval system
US5432942A (en) * 1993-06-10 1995-07-11 The United States Of America As Represented By The Secretary Of The Navy Data structure extraction, conversion and display tool
US5504886A (en) * 1993-07-02 1996-04-02 International Business Machines Corporation System and method for applying user supplied relation definitions to application files for a relational database
BE1005836A6 (en) * 1993-10-05 1994-02-15 L & P Systems Ltd Improvements in the effectiveness of the data processing and related.
US5499358A (en) * 1993-12-10 1996-03-12 Novell, Inc. Method for storing a database in extended attributes of a file system
US5764973A (en) * 1994-02-08 1998-06-09 Enterworks.Com, Inc. System for generating structured query language statements and integrating legacy systems
US5799310A (en) * 1995-05-01 1998-08-25 International Business Machines Corporation Relational database extenders for handling complex data types
CA2151654A1 (en) * 1995-06-13 1996-12-14 William D. Devlin Graphical display method and apparatus
JPH0962547A (en) 1995-08-29 1997-03-07 Nec Software Ltd Data management system
US6208990B1 (en) * 1998-07-15 2001-03-27 Informatica Corporation Method and architecture for automated optimization of ETL throughput in data warehousing applications

Non-Patent Citations (18)

* Cited by examiner, † Cited by third party
Title
D. Merrill, et al., "Codata Tools: Portable Software For Self-Describing Data Files," Computer Science And Statistics: Proceedings of the Fifteenth Symposium on The Interface, Houston, TX, USA, Mar. 1983.
Ellis Horowitz, et al., "V. Mapping A Generic Document Onto The Relational Mode," Software Patent Institute Database of Software Technologies, Record Display, Record 29, Ser. No. iets1208.0089, pp. 855-857, Aug. 1, 1986.
Hansen, "Data Conversion Services," http://www.hansen.com/services/dataconv.html, pp. 1-6, 1997.
MC Barnes, et al., "Storing Hierarchic Database Structures in Transposed Form," Software 73, Loughborough, Leics, UK, Sponsored by: SoftwareWorld, Jul. 9-11, 1973.
Office of The Under Secretary of Defense For Acquistion, "ADA 9X Requirements Rationale: Composition of Program Units," Software Patent Institute Database of Software Technologies, Record Display, Record 25, Ser. No. ADA9XREQ.0023, May 1991.
Philip M. Sargent, "A Tabular Materials Data Interchange Format," http://www.sargents.demon.co.uk/Philip/matdat/tr162-ctdif.html, pp. 1-35, Aug. 1989.* *
Philip M. Sargent, "Technical Data Interchange Using Tabular Formats," Journal of Chemical Information And Computer Sciences, vol. 31, No. 2, pp. 297-300, May 1991. *
Robin Williams, et al., "3. Data Definitions [From [Part I Fundamental Methodology]; Data Structures in Computer Graphics*]," Software Patent Institute Database of Software Technologies, Record Display, Record 5, Ser. No. acadp012.0089, pp. 170-171, Jan. 1, 1977.
RW Lind, "A Simplified Data Structure For Interactive Graphics on a Small Computer," Canadian Computer Conference Session 1972, Montreal, Que., Canada, Sponsored by: Canadian Information Processing Soc., Jun. 1-3, 1972.
S. Abiteboul, "Querying Semi-Structured Data," Database Theory-ICDT '97. 6th International Conference Proceedings, Delphi, Greece, Sponsored by: Nat. Tech. Univ. Athens, Dept. Electr. Comput. Eng., Inst. Commun. & Comput. Syst., Hellenic Telecommun. Organ., et al., Jan. 8-10, 1997.
S. Abiteboul, "Querying Semi-Structured Data," Database Theory—ICDT '97. 6th International Conference Proceedings, Delphi, Greece, Sponsored by: Nat. Tech. Univ. Athens, Dept. Electr. Comput. Eng., Inst. Commun. & Comput. Syst., Hellenic Telecommun. Organ., et al., Jan. 8-10, 1997.
SA Wilson, "Using SAS Views For Data Source Visualization," Proceedings of the Twenty-First Annual SAS Users Group International Conferences, SUGI 21, Chicago, IL, USA, Mar. 10-13, 1996.
Sakti P. Ghosh, "(Part 1 of 4) II. Extension of The Relational Model," Software Patent Institute Database of Software Technologies, Record Display, Record 9, Ser. No. iets1212.0004, pp. 1108-1109, Dec. 1, 1986.
TA Standish, "Data Structure Techniques," Published: Reading, MA, USA, pp. xvi+447, 1980.
W. Dethlefsen, et al., "Computer Storage And Retrieval of Generic Chemical Structures in Patents. XIL. Principles of Search Operations Involving Parameter Lists: Matching-Relations, User-Defined Match Levels, And Transition From The Reduced Graph Search to The Refined Search," Journal of Chemical Information And Computer Sciences, vol. 31, No. 2, pp. 253-260 May 1991.
WTS Deich, "Electrog: An Online Logsheet (Observatories Data Logging)," Proceedings of the SPIE-The International Society For Optical Engineering, vol. 3351, pp. 279-296, 1998.
WTS Deich, "Electrog: An Online Logsheet (Observatories Data Logging)," Proceedings of the SPIE—The International Society For Optical Engineering, vol. 3351, pp. 279-296, 1998.
Youn, C. et al. (IEEE publication, 1992) discloses data migration, Oct. 21, 1992; p. 1255-1258, vol. 2 in Systems, Man and Cybernetics.* *

Cited By (103)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6791585B1 (en) * 2000-01-21 2004-09-14 International Business Machines Corporation Computer method and system for reconciling disparate data archival mediums
US6760019B1 (en) * 2000-06-01 2004-07-06 Sun Microsystems, Inc. Methods and apparatus for facilitating the sharing of computer graphics operations
US7320113B2 (en) 2001-06-15 2008-01-15 Microsoft Corporation Systems and methods for creating and displaying a user interface for displaying hierarchical data
US20050160379A1 (en) * 2001-06-15 2005-07-21 Microsoft Corporation Systems and methods for creating and displaying a user interface for displaying hierarchical data
US6868528B2 (en) * 2001-06-15 2005-03-15 Microsoft Corporation Systems and methods for creating and displaying a user interface for displaying hierarchical data
US20020191033A1 (en) * 2001-06-15 2002-12-19 Scott Roberts Systems and methods for creating and displaying a user interface for displaying hierarchical data
US6782400B2 (en) * 2001-06-21 2004-08-24 International Business Machines Corporation Method and system for transferring data between server systems
US20020198897A1 (en) * 2001-06-21 2002-12-26 International Business Machines Corporation Method and system for transferring data between server systems
US20120323961A1 (en) * 2001-07-18 2012-12-20 Tralee Software Pty. Ltd. Content transfer
US9607064B2 (en) * 2001-07-18 2017-03-28 Semantic Technologies Pty Ltd Content transfer
US9679035B2 (en) * 2001-07-18 2017-06-13 Semantic Technologies Pty Ltd Content transfer
US9378257B2 (en) * 2001-07-18 2016-06-28 Semantic Technologies Pty Ltd Content transfer
US20120254236A1 (en) * 2001-07-18 2012-10-04 Tralee Software Pty. Ltd. Content transfer
US9720988B2 (en) * 2001-07-18 2017-08-01 Semantic Technologies Pty Ltd Content transfer
US9317573B2 (en) * 2001-07-18 2016-04-19 Tralee Software Pty. Ltd. Content transfer
US9767175B2 (en) * 2001-07-18 2017-09-19 Semantic Technologies Pty Ltd Content transfer
US9934296B2 (en) * 2001-07-18 2018-04-03 Semantic Technologies Pty Ltd Content transfer
US20130024451A1 (en) * 2001-07-18 2013-01-24 Tralee Software Pty. Ltd. Content transfer
US20120254235A1 (en) * 2001-07-18 2012-10-04 Tralee Software Pty. Ltd. Content transfer
US20120317140A1 (en) * 2001-07-18 2012-12-13 Tralee Software Pty. Ltd. Content transfer
US20120254237A1 (en) * 2001-07-18 2012-10-04 Tralee Software Pty. Ltd. Content transfer
US20120317139A1 (en) * 2001-07-18 2012-12-13 Tralee Software Pty. Ltd. Content transfer
US20120317071A1 (en) * 2001-07-18 2012-12-13 Tralee Software Pty. Ltd. Content transfer
US20120254260A1 (en) * 2001-07-18 2012-10-04 Tralee Software Pty. Ltd. Content transfer
US20120259899A1 (en) * 2001-07-18 2012-10-11 Tralee Software Pty. Ltd. Content transfer
US20120310978A1 (en) * 2001-07-18 2012-12-06 Tralee Software Pty. Ltd. Content Transfer
US20120310988A1 (en) * 2001-07-18 2012-12-06 Tralee Software Pty. Ltd. Content Transfer
US20120259873A1 (en) * 2001-07-18 2012-10-11 Tralee Software Pty. Ltd. Content transfer
US20120259811A1 (en) * 2001-07-18 2012-10-11 Tralee Software Pty. Ltd. Content transfer
US20120259874A1 (en) * 2001-07-18 2012-10-11 Tralee Software Pty. Ltd. Content transfer
US20120310876A1 (en) * 2001-07-18 2012-12-06 Tralee Software Pty. Ltd. Content transfer
US7089245B1 (en) * 2001-08-31 2006-08-08 Bmc Software, Inc. Service desk data transfer interface
US20060161581A1 (en) * 2001-08-31 2006-07-20 Bmc Software, Inc. Service desk data transfer interface
US9710569B2 (en) 2001-08-31 2017-07-18 Bmc Software, Inc. Service desk data transfer interface
US9792387B2 (en) 2001-08-31 2017-10-17 Bmc Software, Inc. Service desk data transfer interface
US8819084B2 (en) 2001-08-31 2014-08-26 Bmc Software, Inc. Service desk data transfer interface
US20060179070A1 (en) * 2001-08-31 2006-08-10 Bmc Software, Inc. Service desk data transfer interface
US20030105752A1 (en) * 2001-11-27 2003-06-05 General Electric Financial Assurance Holdings, Inc Method and system for performing processing data
US6775683B2 (en) * 2001-11-27 2004-08-10 Ge Financial Assurance Holdings, Inc. Method and system for performing processing data
US7124140B2 (en) * 2001-12-10 2006-10-17 Oracle International Corporation Database system having heterogeneous object types
US7672961B2 (en) * 2001-12-10 2010-03-02 Oracle International Corp. Database having heterogeneous object types
US20030110179A1 (en) * 2001-12-10 2003-06-12 Oracle Corporation Database system having heterogeneous object types
US20070198579A1 (en) * 2001-12-10 2007-08-23 Barton Lee B Database Having Heterogeneous Object Types
US20040083222A1 (en) * 2002-05-09 2004-04-29 Robert Pecherer Method of recursive objects for representing hierarchies in relational database systems
US7548935B2 (en) 2002-05-09 2009-06-16 Robert Pecherer Method of recursive objects for representing hierarchies in relational database systems
WO2004032395A3 (en) * 2002-10-02 2004-10-28 Matter Associates L P System and method for organizing information
US20040068513A1 (en) * 2002-10-02 2004-04-08 Carroll David B. System and method for organizing information
WO2004032395A2 (en) * 2002-10-02 2004-04-15 Matter Associates, L.P. System and method for organizing information
US6873991B2 (en) * 2002-10-02 2005-03-29 Matter Associates, L.P. System and method for organizing information
US7424480B2 (en) 2003-03-10 2008-09-09 Unisys Corporation System and method for storing and accessing data in an interlocking trees datastore
US20060074947A1 (en) * 2003-03-10 2006-04-06 Mazzagatti Jane C System and method for storing and accessing data in an interlocking trees datastore
US7788287B2 (en) 2003-03-10 2010-08-31 Unisys Corporation System and method for storing and accessing data in an interlocking trees datastore
US20050055351A1 (en) * 2003-09-05 2005-03-10 Oracle International Corporation Apparatus and methods for transferring database objects into and out of database systems
US8516004B2 (en) 2003-09-19 2013-08-20 Unisys Corporation Method for processing K node count fields using an intensity variable
US20080065661A1 (en) * 2004-01-16 2008-03-13 Mazzagatti Jane C Saving and restoring an interlocking trees datastore
US7340471B2 (en) 2004-01-16 2008-03-04 Unisys Corporation Saving and restoring an interlocking trees datastore
US20050198617A1 (en) * 2004-03-04 2005-09-08 Vivcom, Inc. Graphically browsing schema documents described by XML schema
US20050262113A1 (en) * 2004-05-14 2005-11-24 Geeta Arora Interpreting remote objects at a local site
US8359336B2 (en) * 2004-05-14 2013-01-22 Oracle International Corporation Interpreting remote objects at a local site
US8554805B2 (en) * 2004-05-17 2013-10-08 Sap Ag Methods and systems for importing source data
US20050257125A1 (en) * 2004-05-17 2005-11-17 Sap Aktiengesellschaft Methods and systems for importing source data
US7593923B1 (en) 2004-06-29 2009-09-22 Unisys Corporation Functional operations for accessing and/or building interlocking trees datastores to enable their use with applications software
US7213041B2 (en) 2004-10-05 2007-05-01 Unisys Corporation Saving and restoring an interlocking trees datastore
US20070143527A1 (en) * 2004-10-05 2007-06-21 Mazzagatti Jane C Saving and restoring an interlocking trees datastore
US7716241B1 (en) 2004-10-27 2010-05-11 Unisys Corporation Storing the repository origin of data inputs within a knowledge store
US7908240B1 (en) 2004-10-28 2011-03-15 Unisys Corporation Facilitated use of column and field data for field record universe in a knowledge store
US7348980B2 (en) 2004-11-08 2008-03-25 Unisys Corporation Method and apparatus for interface for graphic display of data from a Kstore
US20070038654A1 (en) * 2004-11-08 2007-02-15 Mazzagatti Jane C API to KStore interlocking trees datastore
US20070162508A1 (en) * 2004-11-08 2007-07-12 Mazzagatti Jane C Updating information in an interlocking trees datastore
US7418445B1 (en) 2004-11-08 2008-08-26 Unisys Corporation Method for reducing the scope of the K node construction lock
US7499932B2 (en) 2004-11-08 2009-03-03 Unisys Corporation Accessing data in an interlocking trees data structure using an application programming interface
US7571182B1 (en) 2005-01-26 2009-08-04 Star Analytics, Inc. Emulation of a balanced hierarchy from a nonbalanced hierarchy
CN100543737C (en) 2005-02-01 2009-09-23 微软公司 Mechanisms for transferring raw data from one data structure to another structure
US7574516B2 (en) 2005-02-01 2009-08-11 Microsoft Corporation Mechanisms for transferring raw data from one data structure to another representing the same item
EP1686487A3 (en) * 2005-02-01 2007-04-18 Microsoft Corporation Mechanisms for transferring raw data from one data structure to another representing the same item
US20060173933A1 (en) * 2005-02-01 2006-08-03 Microsoft Corporation Mechanisms for transferring raw data from one data structure to another representing the same item
EP1686487A2 (en) * 2005-02-01 2006-08-02 Microsoft Corporation Mechanisms for transferring raw data from one data structure to another representing the same item
US7409380B1 (en) 2005-04-07 2008-08-05 Unisys Corporation Facilitated reuse of K locations in a knowledge store
US7389301B1 (en) 2005-06-10 2008-06-17 Unisys Corporation Data aggregation user interface and analytic adapted for a KStore
US20060280511A1 (en) * 2005-06-14 2006-12-14 Ryutaro Futami Optical receiver having bias circuit for avalanche photodiode with wide dynamic range
US7676477B1 (en) 2005-10-24 2010-03-09 Unisys Corporation Utilities for deriving values and information from within an interlocking trees data store
US20070214153A1 (en) * 2006-03-10 2007-09-13 Mazzagatti Jane C Method for processing an input particle stream for creating upper levels of KStore
US7734571B2 (en) 2006-03-20 2010-06-08 Unisys Corporation Method for processing sensor data within a particle stream by a KStore
US20080275842A1 (en) * 2006-03-20 2008-11-06 Jane Campbell Mazzagatti Method for processing counts when an end node is encountered
US20070220070A1 (en) * 2006-03-20 2007-09-20 Mazzagatti Jane C Method for processing sensor data within a particle stream by a KStore
US20070220069A1 (en) * 2006-03-20 2007-09-20 Mazzagatti Jane C Method for processing an input particle stream for creating lower levels of a KStore
US7689571B1 (en) 2006-03-24 2010-03-30 Unisys Corporation Optimizing the size of an interlocking tree datastore structure for KStore
US20070233723A1 (en) * 2006-04-04 2007-10-04 Mazzagatti Jane C Method for determining a most probable K location
US8238351B2 (en) 2006-04-04 2012-08-07 Unisys Corporation Method for determining a most probable K location
US7676330B1 (en) 2006-05-16 2010-03-09 Unisys Corporation Method for processing a particle using a sensor structure
US20080177870A1 (en) * 2006-12-22 2008-07-24 International Business Machines Corporation Selecting information for ad hoc exchange
US20080243876A1 (en) * 2007-03-30 2008-10-02 International Business Machines Corporation Creation of generic hierarchies
US8032484B2 (en) * 2007-03-30 2011-10-04 International Business Machines Corporation Creation of generic hierarchies
US8595616B2 (en) * 2007-05-31 2013-11-26 Bank Of America Corporation Data conversion environment
US20080301162A1 (en) * 2007-05-31 2008-12-04 Bank Of America Corporation Data conversion environment
US20100145727A1 (en) * 2008-12-08 2010-06-10 Microsoft Corporation Interaction between healthcare software products
WO2011074942A1 (en) * 2009-12-16 2011-06-23 Emanual System Sdn Bhd System and method of converting data from a multiple table structure into an edoc format
US20120089562A1 (en) * 2010-10-04 2012-04-12 Sempras Software, Inc. Methods and Apparatus for Integrated Management of Structured Data From Various Sources and Having Various Formats
CN103455589A (en) * 2013-08-29 2013-12-18 中国农业银行股份有限公司 Product data migration method, device and system in product factory pattern
CN103455589B (en) * 2013-08-29 2016-09-21 中国农业银行股份有限公司 Product data migration method in a factory mode product, apparatus and system
CN103412765A (en) * 2013-09-04 2013-11-27 广东全通教育股份有限公司 Method for realizing universality of data exporting interface
US20160353135A1 (en) * 2014-02-28 2016-12-01 Samsung Electronics Co., Ltd. Method and apparatus for transmitting/receiving signaling information in digital broadcast system
US9864764B2 (en) * 2014-08-29 2018-01-09 Accenture Global Solutions Limited Evolving data archives

Also Published As

Publication number Publication date Type
US6502098B2 (en) 2002-12-31 grant
US20020133510A1 (en) 2002-09-19 application

Similar Documents

Publication Publication Date Title
Varlamis et al. Bridging XML-schema and relational databases: a system for generating and manipulating relational databases using valid XML documents
Papakonstantinou et al. Object fusion in mediator systems
Brodie On the development of data models
Härder et al. PRIMA: A DBMS prototype supporting engineering applications
Stonebraker et al. Extending a database system with procedures
US6453310B1 (en) Installable schema for low-overhead databases
Carey et al. The EXODUS extensible DBMS project: An overview
Melton et al. SQL: 1999: understanding relational language components
US6298342B1 (en) Electronic database operations for perspective transformations on relational tables using pivot and unpivot columns
US7016910B2 (en) Indexing, rewriting and efficient querying of relations referencing semistructured data
US6356913B1 (en) Generic (database-independent) and dynamically-modifiable schema
US6836778B2 (en) Techniques for changing XML content in a relational database
US6581062B1 (en) Method and apparatus for storing semi-structured data in a structured manner
US5596746A (en) Method for transforming relational data base schemas into object models using ideal table meta models
US6985895B2 (en) Performing spreadsheet-like calculations in a database system
US5581758A (en) Computer program product for object specification, generation, and management in a distributed database
US6643633B2 (en) Storing fragmented XML data into a relational database by decomposing XML documents with application specific mappings
US7051039B1 (en) Mechanism for uniform access control in a database system
Lakshmanan et al. SchemaSQL-a language for interoperability in relational multi-database systems
US6154747A (en) Hash table implementation of an object repository
US6708164B1 (en) Transforming query results into hierarchical information
US5694598A (en) Method for mapping data between a relational format and an object-oriented format
Carey et al. A data model and query language for EXODUS
US5615362A (en) Method and apparatus for managing relational data in an object cache
US20030182268A1 (en) Method and system for storing and querying of markup based documents in a relational database

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LAU, LEO TAT MAN;REEL/FRAME:010420/0378

Effective date: 19990915

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

REMI Maintenance fee reminder mailed
FPAY Fee payment

Year of fee payment: 12

SULP Surcharge for late payment

Year of fee payment: 11