SYSTEM AND METHOD FOR CONVERTING AND STORING DATA VALUES

• US 20090282073A1
• Filed: 05/09/2008
• Published: 11/12/2009
• Est. Priority Date: 05/09/2008
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Roden, Bari Jane
• Granted Patent: US 7,890,538 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

A system and associated method for converting and storing data values. Receiving multiple primary keys, each primary key being associated with a unique table in a plurality of tables; multiple foreign keys, each foreign key being associated with at least two tables in the plurality of tables; and multiple datasets; each dataset containing a schema for a single table. Creating a schema control card identifying the primary keys, foreign keys, datasets'"'"' location, and identifies a path to traverse the tables. Creating either a storage control to store data values from the plurality of tables to a storage location, or creating a retrieval control card to retrieve a storage value from the storage location and return to the plurality of tables. The tables are traversed via the path and data values are either stored using the storage control card or retrieved using the retrieval control card.

Claims

1. A method for converting and storing data values comprising:

receiving a plurality of primary keys and a plurality of foreign keys, each primary key in said plurality of primary keys being associated with a unique table of a plurality of tables, each foreign key in said plurality of foreign keys being associated at least two tables of said plurality of tables, each table in said plurality of tables being relationally related to at least one other table in said plurality of tables, wherein each table in said plurality of tables contains a first plurality of data values;

receiving a plurality of datasets, each dataset in said plurality of datasets comprising a collection of schema for a unique table of said plurality of tables;

after said receiving said plurality of primary keys and said plurality of foreign keys, after said receiving a plurality of datasets, creating a schema control card, said schema control card comprising a list that includes said plurality of primary keys, said plurality of foreign keys, a location for said plurality of datasets, and a list comprising a path to traverse said plurality of tables;

after said creating said schema control card, creating a storage control card or creating a retrieval control card, said storage control card comprising;

a list that includes a location for said schema control card;

a data value located in at least one table of said plurality of tables, a storage location;

a first storage value data type; and

a boolean value identifying whether said first storage value replaces a previously stored first storage value located in said storage location, said retrieval control card comprising;

a list that includes said location for said schema control card;

said storage location; and

a row number of a row of said plurality of rows, and

after said creating said storage control card or said creating said retrieval control card, traversing said plurality of tables utilizing said storage control card or traversing said plurality of table utilizing said retrieval control card, respectively.

2. The method of claim 1, each dataset in said plurality of datasets being a unique list comprising a table name, a list of table fields, a list of data types, and a list of data lengths, each data type in said list of data types being associated with a unique table field in said plurality of table fields, each data length being associated with a unique table field in said plurality of table fields.

3. The method of claim 1, said first storage value data type being a string.

4. The method of claim 1, said storage location being a database table consisting of a plurality of rows and a plurality of columns residing in a relational database environment.

5. The method of claim 1, said traversing said plurality of tables utilizing said storage control card comprising:

converting and storing a second plurality of data values utilizing both said schema control card and said storage control card, said second plurality of data values being a subset of said first plurality of data values, said converting and said storing comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

converting each data value relationally related to said data value into said first storage value; and

storing said first storage value in said storage location according to said boolean value.

6. The method of claim 1, said traversing said plurality of tables utilizing said retrieval control card comprising:

converting and restoring a unique storage value located at said row having said row number in said storage location utilizing said schema control card and said retrieval control card, said converting and said restoring comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

for each table field in each table of said plurality of tables, removing a second storage value from a beginning of said first storage value, said second storage value having a length equal to said data length associated with said table field, converting said second storage value from said first storage value data type to said data type associated with said table field, and storing said second storage value in each table.

7. A computer program product, comprising a computer-usable storage medium having a computer-readable program code stored therein, said computer-readable program code containing instructions that when executed by a processor of a computer system implement a method for converting and storing data values comprising:

receiving a plurality of primary keys and a plurality of foreign keys, each primary key in said plurality of primary keys being associated with a unique table of a plurality of tables, each foreign key in said plurality of foreign keys being associated at least two tables of said plurality of tables, each table in said plurality of tables being relationally related to at least one other table in said plurality of tables, wherein each table in said plurality of tables contains a first plurality of data values;

receiving a plurality of datasets, each dataset in said plurality of datasets comprising a collection of schema for a unique table of said plurality of tables;

after said receiving said plurality of primary keys and said plurality of foreign keys, after said receiving a plurality of datasets, creating a schema control card, said schema control card comprising a list that includes said plurality of primary keys, said plurality of foreign keys, a location for said plurality of datasets, and a list comprising a path to traverse said plurality of tables;

after said creating said schema control card, creating a storage control card or creating a retrieval control card, said storage control card comprising;

a list that includes a location for said schema control card;

a data value located in at least one table of said plurality of tables, a storage location;

a first storage value data type; and

a boolean value identifying whether said first storage value replaces a previously stored first storage value located in said storage location, said retrieval control card comprising;

a list that includes said location for said schema control card;

said storage location; and

a row number of a row of said plurality of rows, and

after said creating said storage control card or said creating said retrieval control card, traversing said plurality of tables utilizing said storage control card or traversing said plurality of table utilizing said retrieval control card, respectively.

8. The computer program product of claim 7, each dataset in said plurality of datasets being a unique list comprising a table name, a list of table fields, a list of data types, and a list of data lengths, each data type in said list of data types being associated with a unique table field in said plurality of table fields, each data length being associated with a unique table field in said plurality of table fields.

9. The computer program product of claim 7, said first storage value data type being a string.

10. The computer program product of claim 7, said storage location being a database table consisting of a plurality of rows and a plurality of columns residing in a relational database environment.

11. The computer program product of claim 7, said traversing said plurality of tables utilizing said storage control card comprising:

converting and storing a second plurality of data values utilizing both said schema control card and said storage control card, said second plurality of data values being a subset of said first plurality of data values, said converting and said storing comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

converting each data value relationally related to said data value into said first storage value; and

storing said first storage value in said storage location according to said boolean value.

12. The computer program product of claim 7, said traversing said plurality of tables utilizing said retrieval control card comprising:

converting and restoring a unique storage value located at said row having said row number in said storage location utilizing said schema control card and said retrieval control card, said converting and said restoring comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

for each table field in each table of said plurality of tables, removing a second storage value from a beginning of said first storage value, said second storage value having a length equal to said data length associated with said table field, converting said second storage value from said first storage value data type to said data type associated with said table field, and storing said second storage value in each table.

13. A computing system comprising a processor coupled to a computer-readable memory unit, said memory unit comprising a software application, said software application comprising instruction that when executed by said processor, implement a method for converting and storing data values comprising:

receiving a plurality of primary keys and a plurality of foreign keys, each primary key in said plurality of primary keys being associated with a unique table of a plurality of tables, each foreign key in said plurality of foreign keys being associated at least two tables of said plurality of tables, each table in said plurality of tables being relationally related to at least one other table in said plurality of tables, wherein each table in said plurality of tables contains a first plurality of data values;

receiving a plurality of datasets, each dataset in said plurality of datasets comprising a collection of schema for a unique table of said plurality of tables;

after said receiving said plurality of primary keys and said plurality of foreign keys, after said receiving a plurality of datasets, creating a schema control card, said schema control card comprising a list that includes said plurality of primary keys, said plurality of foreign keys, a location for said plurality of datasets, and a list comprising a path to traverse said plurality of tables;

after said creating said schema control card, creating a storage control card or creating a retrieval control card, said storage control card comprising;

a list that includes a location for said schema control card;

a data value located in at least one table of said plurality of tables, a storage location;

a first storage value data type; and

a boolean value identifying whether said first storage value replaces a previously stored first storage value located in said storage location, said retrieval control card comprising;

a list that includes said location for said schema control card;

said storage location; and

a row number of a row of said plurality of rows, and

after said creating said storage control card or said creating said retrieval control card, traversing said plurality of tables utilizing said storage control card or traversing said plurality of table utilizing said retrieval control card, respectively.

14. The computer system of claim 13, each dataset in said plurality of datasets being a unique list comprising a table name, a list of table fields, a list of data types, and a list of data lengths, each data type in said list of data types being associated with a unique table field in said plurality of table fields, each data length being associated with a unique table field in said plurality of table fields.

15. The computer system of claim 13, said first storage value data type being a string.

16. The computer system of claim 13, said storage location being a database table consisting of a plurality of rows and a plurality of columns residing in a relational database environment.

17. The computer system of claim 13, said traversing said plurality of tables utilizing said storage control card comprising:

converting and storing a second plurality of data values utilizing both said schema control card and said storage control card, said second plurality of data values being a subset of said first plurality of data values, said converting and said storing comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

converting each data value relationally related to said data value into said first storage value; and

storing said first storage value in said storage location according to said boolean value.

18. The computer system of claim 13, said traversing said plurality of tables utilizing said retrieval control card comprising:

converting and restoring a unique storage value located at said row having said row number in said storage location utilizing said schema control card and said retrieval control card, said converting and said restoring comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

for each table field in each table of said plurality of tables, removing a second storage value from a beginning of said first storage value, said second storage value having a length equal to said data length associated with said table field, converting said second storage value from said first storage value data type to said data type associated with said table field, and storing said second storage value in each table.

19. A process for supporting computer infrastructure, said process comprising providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable code in a computing system, wherein said code in combination with the computing system is capable of implementing 1 method for converting and storing data values comprising:

receiving a plurality of primary keys and a plurality of foreign keys, each primary key in said plurality of primary keys being associated with a unique table of a plurality of tables, each foreign key in said plurality of foreign keys being associated at least two tables of said plurality of tables, each table in said plurality of tables being relationally related to at least one other table in said plurality of tables, wherein each table in said plurality of tables contains a first plurality of data values;

receiving a plurality of datasets, each dataset in said plurality of datasets comprising a collection of schema for a unique table of said plurality of tables;

after said receiving said plurality of primary keys and said plurality of foreign keys, after said receiving a plurality of datasets, creating a schema control card, said schema control card comprising a list that includes said plurality of primary keys, said plurality of foreign keys, a location for said plurality of datasets, and a list comprising a path to traverse said plurality of tables;

after said creating said schema control card, creating a storage control card or creating a retrieval control card, said storage control card comprising;

a list that includes a location for said schema control card;

a data value located in at least one table of said plurality of tables, a storage location;

a first storage value data type; and

a boolean value identifying whether said first storage value replaces a previously stored first storage value located in said storage location, said retrieval control card comprising;

a list that includes said location for said schema control card;

said storage location; and

a row number of a row of said plurality of rows, and

after said creating said storage control card or said creating said retrieval control card, traversing said plurality of tables utilizing said storage control card or traversing said plurality of table utilizing said retrieval control card, respectively.

20. The process of claim 19, each dataset in said plurality of datasets being a unique list comprising a table name, a list of table fields, a list of data types, and a list of data lengths, each data type in said list of data types being associated with a unique table field in said plurality of table fields, each data length being associated with a unique table field in said plurality of table fields.

21. The process of claim 19, said first storage value data type being a string.

22. The process of claim 19, said storage location being a database table consisting of a plurality of rows and a plurality of columns residing in a relational database environment.

23. The process of claim 19, said traversing said plurality of tables utilizing said storage control card comprising:

converting and storing a second plurality of data values utilizing both said schema control card and said storage control card, said second plurality of data values being a subset of said first plurality of data values, said converting and said storing comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

converting each data value relationally related to said data value into said first storage value; and

storing said first storage value in said storage location according to said boolean value.

24. The process of claim 19, said traversing said plurality of tables utilizing said retrieval control card comprising:

converting and restoring a unique storage value located at said row having said row number in said storage location utilizing said schema control card and said retrieval control card, said converting and said restoring comprising;

utilizing said plurality of primary keys, said plurality of foreign keys, and said plurality of datasets to traverse said plurality of tables according to said path;

for each table field in each table of said plurality of tables, removing a second storage value from a beginning of said first storage value, said second storage value having a length equal to said data length associated with said table field, converting said second storage value from said first storage value data type to said data type associated with said table field, and storing said second storage value in each table.