Patent Application
20070094233
The subject matter described herein relates to the combination of multi-dimensional data sources using database operations. Within relational databases, an important tool for linking information is the join. A join links the contents of two or more database tables (referred to hereinafter simply as “tables”). The result of the linking is displayed in the form of another table.
The combining of tables is described using one or more ON conditions within a select statement. An ON condition describes a condition between two tables, whereby one field of each table has to be contained in this condition. Equal join conditions are usually used. They have the format: Field1(Table1)=Field2(Table2). Database systems typically permit any ON conditions. A result set is generated when a join is processed. The following instances are based on the assumption that all fields of all tables are contained in the result set. This is possible without restrictions, so long as the process of obtaining the result set is of most interest.
A table is referred to as Ti, a record of this table is referred to as ti∈Ti. A record which contains initial values only is referred to as ε. Linking two tables with a join is referred to with T1 join T2 or T1 left outer join T2. The result set is referred to as TE. A record in the result set tE∈TE has the structure tE=(t1, . . . , tn). Each subrecord ti∈Ti is a record of table Ti that is contained in the join. The fields of a record in a table Ti are called field(ti). Within system query language (SQL) statements, for example, tables are called T1 and their fields are referred to as T1 FIELD.
First the result set is determined on the basis of the ON conditions. The result set is then restricted on the basis of a WHERE condition. The result set fulfills the following conditions: every record contains, for every table affected, an element whose structure corresponds to the structure of the table; all ON conditions within a record are fulfilled; all WHERE conditions within a record are fulfilled; and there are no combinations of data records in the database which fulfill the ON and WHERE conditions but which are not contained in the result set.
The following method describes the first step in calculating the result set for two tables T1 and T2, where only the ON conditions are taken into consideration.
Method 1: T1 join T2
1. Examine each record t1∈T1 in accordance with the second step.
2. Compare each record t2∈T2 with record t1. If the ON conditions are fulfilled then insert a record tE=(t1, t2) into the result set.
This method only determines the way in which the result set is generated. Most database systems use other, more effective methods. If more than two tables are involved, method 1 can be used, but must be applied in several steps. The sequence of the tables is arbitrary. With regard to method 1, each record t1∈T1 or t2∈T2 can appear as a subrecord in several records of the result set, and a record t1∈T1 or t2∈T2 may not appear as a subrecord in the result set at all.
In many evaluations, the second case is not desirable. Users often want a record from one of the tables in the result set, even if no suitable record exists in the corresponding table. Therefore, in the SQL standard, so-called outer joins are defined. In this document, only left outer joins are discussed. With a left outer join, method 1 has to be enhanced slightly.
Method 2: T1 left outer join T2
1. Examine each record t1∈T1 in accordance with the second step
2. Compare each record t2∈T2 with record t1 . If the ON conditions are fulfilled, insert a record tE=(t1, t2) into the result set. If at least one data record is inserted into the result set in this way, return to step 1. Otherwise go to step 3.
3. Insert a record tE=(t1, ε) into the result set where the values of subrecord t2 are initial.
This method can also be used if more than two tables are involved. It then has to be applied in several steps. In this case the sequence of the tables is no longer arbitrary. This document does not cover all the problems that can occur when left outer joins are used.
The join methods described above are best suited for flat structures, such as database tables. In the context of a business warehouse, however, multidimensional data structures (InfoCubes) are usually used for evaluations, where key figures are characterized by a multiplicity of characteristics that are arranged in different dimensions. Additionally, data structures of this type often need to be combined with other multidimensional or one-dimensional data structures using a type of join. Therefore, joins for multidimensional data sources must have effective access paths.
Joins between time-dependent tables represent a further problem. In a time-dependent table each record contains one time interval which determines the period in which this record is valid. The time interval can be determined either by two dates (start date and end date) or by a time characteristic (week, month, year etc.).
If two time-dependent tables are connected by a join, it is intuitive that a record can only be a member of the result set if the subrecords of both tables have the same time interval. These time intervals do not have to be identical; the time intervals of the two records can overlap. Appropriate ON conditions have to be formulated. For this, however, the usual equal conditions are no longer adequate. A further problem occurs if the time intervals in the two tables are specified in a different way. For example, one table uses a time characteristic e.g. month, and the other table uses two single dates to define the interval. In particular, this case arises with multidimensional data structures where the use of time characteristics is very common.
InfoSets are a type of InfoProvider. An InfoProvider represents a view of data that can be used to define queries. At runtime, the query instructs the InfoProvider to supply data. The query defines the data that is needed and the selection criteria that are used. InfoSets are virtual InfoProviders as they do not contain their “own” data but represent a view based on existing data sources. This means that several InfoSets can be defined using an existing data source.
Using an InfoSet as an additional InfoProvider is often not worthwhile, as queries can be defined for an individual data source using a different InfoProvider. This is the case, for example, with DataStore objects and master data (characteristics containing master data). For this reason, the essential characteristic of an InfoSet is that it allows several data sources to be linked using a join and in that way, provides information that cannot be provided using other InfoProviders.
Because the definition of joins (as described above) always refers to tables, the following restrictions exist when defining InfoSets: data sources can only be linked that possess a flat (tabular) structure; data sources can only be linked that are represented in the database; and the use of left outer joins must be limited in accordance with the guidelines for the database. These restrictions ensure that the calculation of joins within the database is possible and achieves a desired level of performance.
These restrictions mean that only DataStore objects and master data can be counted as usable DataSources. Equal conditions can only be used as ON conditions when defining InfoSets. Therefore, in the user interfaces, the fields are linked simply with lines. The values of the field have to be equal in a data record in the result set.
In many database systems, master data, or characteristics containing master data, can be defined as time-dependent. In this case the following rules apply: the attributes for one value of the characteristic are only valid for a certain period (this period is described by two dates—start date and end date; and for one value of the characteristic, exactly one valid record exists for each time. 01.01.1000 (dd.mm.yyyy) and 31.12.9999 (dd.mm.yyyy) are used in as the start and end date of the infinite time bar.
With regard to the first rule it is clear that several records can exist in the database for each value of a characteristic, whereby a record always describes exactly one time interval. The second rule guarantees that exactly one value can be determined for the attributes for each point in time. There are no gaps and no overlapping intervals. In order to guarantee this, extensive measures have to be taken when loading master data into the database system. The second rule also ensures that it is always possible to determine the attributes for one given value of a characteristic in a simple way. This means that techniques such as a left outer join are not needed. Within most database systems, characteristics are the only InfoProviders that contain “real” time-dependent data.
When two time-dependent data sources are joined, it is intuitive that two records in tables T1 and T2 can only be contained in a record in the result set if the time intervals for the two records overlap. The tables shown in
This join allows questions to be answered with regard to the combination of persons responsible for profit centers and persons responsible for cost centers. For example, the operation asks which persons were responsible for the cost center and profit center on 01.09.2001. Or, the operation determines an overview of assignments between persons responsible for the profit center and cost center 4711. To explain the results for the second question, consider the time bar shown in
If the equal conditions indicated in
The result of this query is shown in
The common time interval is called a valid time interval and represents a substantial amount of information for each record in the result set. As with time-dependent data sources, the validity of each record is determined by a start date and an end date. The validity of each record in the result set also has to be described by a start date and an end date. Therefore, the result of a join which contains at least one time-dependent data source has to be handled as if it were a time-dependent data source.
The start date of the valid time interval is the earliest of the two start dates and the end date of the valid time interval is the latest of the two end dates. For the two invalid records (3 and 4), calculating the valid time interval shows that the start date is greater than the end date. A prerequisite of a valid data record in the result set is that it has a valid time interval that is “not empty.”
To calculate valid time intervals, method 3 is as follows:
TE is the result set of join T1 join . . . join Tn.
For each record tE=(t1, . . . , tn)∈TE
DATEFROM(tE)=maximum(DATEFROM(ti)) and
DATETO(tE)=minimum(DATETO(ti))
is valid for all i, 1<i<n and T1 is time-dependent.
A valid record exists if the following condition is fulfilled:
Condition 1: Validity of a record of T1 join T2. Two records t1∈T1 and t2 ∈T2 from the time-dependent tables T1 and T2 possess an overlapping time interval in the join T1 join T2 if the following two conditions are fulfilled.
Conditions like these can be evaluated from the database.
This ensures that the database only reads records that have overlapping time intervals and are valid. If the valid time interval is requested by the query for evaluation, method 3 is used. This method is also executed for InfoSets for postprocessing after the data has been read by the database. In principle, this method could also be formulated in SQL statements and executed by the database. If more than two time-dependent tables exist within the join, the principle is similar and can be enhanced to incorporate more time-dependent tables. The condition formulated above must be applied to each pair T1 and Tj of the time-dependent tables.
Condition 2: Validity of a record of T1 join . . . join Tn
A record tE=(t1, . . . , tn) of the result set TE of join T1 join . . . join Tn is valid if for each pair ti∈T1 and tj∈Tj, 1<i, j<n, where T1 and Tj are time-dependent, the following condition is valid:
In an example where three tables are used, these conditions produce the following SQL statement:
Very complex SQL statements can be built very quickly. For this reason, the part of the ON conditions that realizes the calculation of the validity of a data record is generated automatically at the runtime of the InfoSet. The examination and evaluation of the time dependency takes place implicitly and cannot be influenced by the InfoSet author.
As described above, in most database systems only master data can be defined as time-dependent. In this case, two additional internal attributes (start date and end date) are added to the characteristic. The system ensures that neither gaps nor overlaps occur on the time axis. Other InfoProviders (such as DataStore objects and InfoCubes) cannot be defined as time-dependent. However, in many cases, they do contain attributes of type date, or common time characteristics which can be used to describe a time interval.
InfoProvider date specifications of this type or time characteristics in InfoProviders can be used within an InfoSet in order to describe the validity of each data record. In this case, the InfoProvider is treated as a ‘real’ time-dependent data source. This is referred to as pseudo time dependency. Pseudo time dependency can be defined in two ways: 1) one date is specified as the start date and another as the end date for one InfoProvider in the InfoSet; or 2) a time characteristic that can be used to derive a time interval is selected in an InfoProvider in the InfoSet. Two additional date attributes of type date are added automatically to the InfoProvider within the InfoSet (‘valid_from’ —start date and ‘valid_to’ —end date).
As soon as an InfoProvider has been defined as pseudo time-dependent in one of the ways described above, the InfoProvider is treated as a “real” time-dependent data source. For example, a data record in an InfoProvider contains the time characteristic 0CALMONTH-calendar year/month; the value of the time characteristic is 2004.09 (yyyy.mm). This value is be used to derive a start date (01.09.2004) (dd.mm.yyyy) and an end date (30.09.2004) (dd.mm.yyyy). This time interval defines the validity of the data record.
While working with a pseudo time-dependent InfoProvider, the database system cannot prevent gaps occurring on the time axis or time intervals overlapping. This depends on the dataset for the InfoProvider in question. If single date specifications are used to define time dependency, the characteristic values of these date attributes have to be read. Further, the data record has to be “suitable,” which means the value of the start date for the characteristic has to be less than the value of the end date for the characteristic. If the value of the end date is less than the value of the start date, the data record is invalid and will not be read during the request.
The ON conditions between the individual InfoProviders are defined in the InfoSet definition. For the definition, lines are drawn between the attributes of the InfoProviders. These attributes are implicitly connected by an equal join condition. If one of the InfoProviders is a ‘real’ time-dependent InfoProvider, all actions that are necessary to evaluate time dependency are derived from the fact that the InfoProvider is time-dependent. This means that no further actions are required on the user interface.
For pseudo time dependency, one or more InfoProviders have to be defined as pseudo time-dependent. These InfoProviders are then regarded as time-dependent and are treated in exactly the same way as real time-dependent InfoProviders within the InfoSet.
As described in the previous section, two possibilities exist for defining pseudo time dependency. One way is to use two single date specifications. The InfoProvider that is to be defined as pseudo time-dependent must contain at least two attributes of type date. It is pseudo time-dependent due to the fact that one of these attributes is specified as a start date and another as an end date. These entries are made in a separate dialog box in the user interface, as shown in
Another way of defining pseudo time dependency is to use time characteristics. The InfoProvider must contain at least one time characteristic. It is pseudo time-dependent if a time characteristics is selected. Again, this takes place in a separate dialog box, as shown in
In this case, the time characteristic OCALMONTH (calendar month)—field alias F16—is derived. After it has been defined in the separate dialog box, it is displayed in two additional columns (‘from’ and ‘to’). The additional attributes for the start date and end date are: 0DATEFROM-(valid from)—field alias F32; ODATETO-(valid to)—field alias F33. For join operations, what is needed is a mechanism for evaluating time dependency.
This document describes a method and system for linking the contents of two or more tables in a multidimensional data source, where the contents of the tables are at least partially time-independent. In accordance with one aspect, a computer-implemented method of linking the contents of two or more at least partially time-independent tables in a multidimensional data source includes determining a pseudo time dependency between the two or more at least partially time-independent tables. The method further includes generating a first time interval for the join operation based on the pseudo time dependency, and executing a join operation using the first time interval.
In another aspect, a computer-implemented method includes generating a join operation for the two or more at least partially time-independent tables, the join operation including a query instruction executable on the multidimensional data source, where the query instruction has at least one time attribute. The method further includes the steps of determining a pseudo time dependency between the two or more at least partially time-independent tables, generating a time interval for the join operation based on the pseudo time dependency, executing the join operation using the time interval as the at least one time attribute.
The details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.
These and other aspects will now be described in detail with reference to the following drawings.
Like reference symbols in the various drawings indicate like elements.
This document describes various systems and methods by which time dependency is evaluated when pseudo time-dependent InfoProviders are used. Different cases are described that reflect the different definition options (using two specific dates or using a time characteristic) and the type of operations executed (for example, inner join or left outer join, etc.).
In a first case, using an inner join and two specific attributes of type date, an InfoProvider is defined as pseudo time-dependent since a date has been selected as the start date and another date as the end date. These define the valid time interval. This InfoProvider is connected to another InfoProvider using an inner join condition, as graphically depicted in
In this case, the attributes F28 (Date—01) and F29 (Date—02) of InfoProvider sponsor (T00003-CROSPONS) are interpreted as the start date and end date. With this definition, the same logic can be used to determine the data as is used for ‘real’ time-dependent characteristics. As all the conditions are used in the SQL statement the data provided by the database does not require postprocessing.
This SQL statement shows that the start date (Date—01) and the end date (Date—02) of the pseudo time-dependent InfoProvider are handled in the same way as the fields valid_from and valid_to in the ‘real’ time-dependent InfoProvider.
In a second case, using an inner join and time characteristic, an InfoProvider is defined as pseudo time-dependent since a time characteristic that can be used to derive a start date and an end date has been selected. Two internal attributes of type date are added to the InfoProvider. The InfoProvider is connected to another InfoProvider using an inner join, as depicted in
In this case, attribute F22 (OCALMONTH, Calendar Year/Month) of InfoProvider sponsor (T00003-CROSPONS) is used. The attributes of type date which are added internally are F26 (valid from-start date) and F27 (valid to-end date). Since the start date and end date are not available as individual database fields they cannot be used in the SQL statement. That means that the SQL statement, as shown below, is built first, without taking the pseudo time dependency into account.
Accordingly, too many data records may be read and the records will require postprocessing. In accordance with
The valid time interval (valid_from and valid_to) is determined first only from the two InfoProviders ‘costcenter’ and ‘profit center’. In the subsequent step, the start date and end date are calculated for each data record using the value of the calendar month (F22):
The system then checks every data record to see whether the derived time interval overlaps with the valid time interval that had already been determined by the SQL statement (only ‘costcenter’ and ‘profit center’ have been taken into account). If this is not the case, the data record is deleted. The following data records represent the final result and the expected result:
A first method for determining the result set is set forth below, and assumes that TE is the result set of join T1 join . . . join Tn. At least one of the tables Ti is defined as pseudo time-dependent and uses a time characteristic to derive the start date and the end date. TE was determined using an SQL statement which contained a superset of the result set.
Result set TE′ is determined from TE. A record tE′ =(t1′, . . . , tn′) is determined for each data record tE=(t1, . . . , tn)∈TE. With the determination of data record tE′ from tE=(t1, . . . , tn) which applies to all i, 1<i<n. If T1 is not pseudo time-dependent, ti=ti′. If Ti is pseudo time-dependent, ti′ results from ti by calculating the start date and the end date. Both are derived from the time characteristic that is defined in the InfoProvider. As soon as all ti′, 1<i<n are determined, the valid time interval for record tE′ is calculated according to algorithm 3. If the result is not empty, the data record it added to the result set TE′ —otherwise the data record will be deleted. TE′ is the result set of join T1 join . . . join Tn.
It is possible that the time interval derived from the time characteristic has already been calculated and transferred to the database. Databases provide so-called UDFs (user defined functions) for this purpose. Fields that are calculated by the database using a UDF can be included in the SQL statement just like existing database fields.
In some cases, deriving the time interval from the time characteristic is a relatively simple process. For example, the start date and end date can be calculated fairly easily if the time characteristic is a calendar month (0CALMONTH) or a calendar year (0CALYEAR). Time characteristics of this type are candidates for using UDFs. Other time characteristics, for example the fiscal year (0FISCYEAR) or the fiscal year/period (0FISCPER), are too complicated in their logic to use a UDF to calculate their start and end date. For these reasons, only the fields which already exist in the format of type date are used in the SQL statement.
In a third case, using a left outer join and two attributes of type date, an InfoProvider is defined as pseudo time-dependent if one date has been selected as the start date and another as the end date. These two dates define the valid time interval. This InfoProvider is connected to another InfoProvider using a left outer join condition.
The following example of the third case is similar to the example in the first case described above. A difference is that the InfoProvider sponsor (T00003-CROSPONS) is defined as a left outer InfoProvider. In the user interface, as shown in
Here the same logic can be used to obtain the result set and determine the valid time interval as is used with ‘real’ time-dependent characteristics. The SQL statement is as follows:
The result set of the SQL statement is as follows:
In a fourth case, using a left outer join and a time characteristic, an Infoprovider is defined as pseudo time-dependent if a time characteristic which can be used to derive a start date and an end date has been selected. Two internal attributes of type date have been added to the InfoProvider. The InfoProvider is connected to another InfoProvider using a left outer join. The following example of the fourth case is similar to the example of the second case. The only difference is that the InfoProvider sponsor (T00003-CROSPONS) is defined as a left outer InfoProvider, as shown in
Since the start date and the end date are not available as individual database fields, they cannot be used in the SQL statement. Thus, the SQL statement is first built without taking the pseudo time dependency into account, as follows:
The SQL statement first returns the same result set, as described above. To facilitate better understanding of the postprocessing, two additional columns (‘valid_from’ and ‘valid_to’) are added that describe the time interval of the InfoProviders ‘costcenter’ and ‘profitcenter’, as shown below:
As described above, too many data records may be read and the records will therefore require postprocessing, as F22 (0CALMONTH calendar year/month) is not used in the SQL statement. However, the postprocessing of data records must be organized differently than in the earlier example because of the left outer join condition. The start date and end date are subsequently calculated for each data record using the value of the calendar month (F22):
The system checks each data record to see whether the derived time interval overlaps with the valid time interval that was calculated previously (only taking cost center and profit center into account). If this is the case, the data record remains in the result set. However, even if this is not the case, the data record may not be deleted because at least one data record has to remain in the result set where the left outer part is initial. Therefore all the fields from the left outer part are initialized first.
An intermediate result is then generated. If a time overlap exists, the values of the valid time interval (valid_from and valid_to) are adapted if necessary. Otherwise the values (valid_from and valid_to) remain unchanged.
Next the intermediate result is sorted by the keys of the inner parts as well as by the valid time intervals of the inner parts (F1, F13, F14, F3, F11, F12, F19, F20). The sort sequence is shown in the following graphic table. Data records that have the same sort key values can be easily identified by the zebra pattern.
Next the system examines each group that has the same sort key values. Within a group of this type, data records may exist that have initial left outer values. This is the case if the derived valid time interval of the left outer part does not overlap with the valid time interval that has been calculated previously. In addition, data records may exist which have values in their left outer part that are not initial. This is the case if the derived valid time interval of the left outer part does overlap with the valid time interval that has been calculated previously.
If the left outer parts of all data records within one group are initial, then no data records exist for the left outer table. According to left outer join definition, exactly one data record with an initial left outer part has to be added to the result set. If some left outer parts of all of the data records within one group are initial, and some parts contain values that are not initial, then one or more left outer table data records exist. In this case, the data records with the initial left outer parts must not be added to the result set, while all other data records which do contain values in their left outer parts that are not initial must be added to the result set.
The first and second data records illustrate this point: In this case the second data record contains a left outer part that is not initial. Therefore the first data record can be deleted and the second data record is added to the result set. The same is true of the seventh and eighth data records. For the third and fourth data records, both left outer parts are initial. In this case, only one data record is added to the result set, and all other records of this group have to be deleted. The same is true of the fifth and sixth data records. The final result is as follows:
If the time intervals of the InfoProviders ‘cost center’ and ‘profit center’ are not taken into account, the result is as follows:
This result corresponds with the result in of the third case.
The following description provides a method by which an unrestricted number of InfoProviders to be connected using a left outer join condition.
TE is the result set of join T1 join . . . join Tn. At least one of the tables Ti was defined as pseudo time-dependent, using a time characteristic to derive the start date and end date. In addition, this table has to be connected to another InfoProvider using a left outer join operation. TE was first determined using a SQL statement which contained a superset of the final result set.
In the following, tables that are connected using an inner or left outer join are called ‘inner joins’ and ‘left outer joins’ respectively. Result set TE′ is determined from TE. A record tE′ =(t1′, . . . , tn′) is determined for each data record tE=(t1, . . . , tn) Î TE. With the determination of data record tE′ from tE=(t1, . . . , tn) which applies to all i, with l<i<n. If Ti is not pseudo time-dependent, then ti=ti′. If Ti is pseudo time-dependent, then ti′ results from ti by calculating the start date and the end date. Both are derived from the time characteristic that are defined in the InfoProvider.
As soon as each ti′, 1<i<n of a data record tE′ is determined, the preliminary valid time interval is calculated as described above, only taking the inner parts into account. If the preliminary valid time interval is empty, the data record tE′ =(1t1′, . . . , tn′) is deleted and will not be added to the final result TE′ set. If the preliminary valid time interval is not empty, each data record ti′ which is part of an outer table is checked.
The data record is retained if the time interval which is derived from the time characteristic (left outer part) overlaps with the time interval that has been calculated previously (inner parts). The data record ti′ (left outer part) is initialized if the time interval which is derived from the time characteristic (left outer part) does not overlap with the time interval that has been calculated previously (inner parts).
The valid time interval is then recalculated in accordance with algorithm 3 and all InfoProviders are now taken into account. Tables ti′ which have initial values are not included. If the time interval is rendered invalid (condition 2 from section 2.3 is not fulfilled), the data record tE′=(t1′, . . . , tn′) is deleted and will not be added to the result set TE′. Next the result set TE′ is sorted. All fields of all inner tables ti′ are taken as sort keys, including the fields describing the time intervals of these tables.
The data records are then checked in one group of table TE′ which have the same sort key values. The data records are added to the result set if the fields of at least one left outer part in one group are not initial. In this case, all the data records with initial values in each left outer part are deleted and are not added to the result set. If all of the data records in one group have initial values in each left outer part, all but one of the data records are deleted from this group and from the final result set. The final result set TE′ consists of the data records of each group.
Embodiments of the invention and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of them. Embodiments of the invention can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer readable medium, e.g., a machine readable storage device, a machine readable storage medium, a memory device, or a machine-readable propagated signal, for execution by, or to control the operation of, data processing apparatus.
The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
A computer program (also referred to as a program, software, an application, a software application, a script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices.
Information carriers suitable for embodying computer program instructions and data include all forms of non volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the invention can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
Embodiments of the invention can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the invention, or any combination of such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Certain features which, for clarity, are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features which, for brevity, are described in the context of a single embodiment, may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
Particular embodiments of the invention have been described. Other embodiments are within the scope of the following claims. For example, the steps recited in the claims can be performed in a different order and still achieve desirable results. In addition, embodiments of the invention are not limited to database architectures that are relational; for example, the invention can be implemented to provide indexing and archiving methods and systems for databases built on models other than the relational model, e.g., navigational databases or object oriented databases, and for databases having records with complex attribute structures, e.g., object oriented programming objects or markup language documents. The processes described may be implemented by applications specifically performing archiving and retrieval functions or embedded within other applications.
The present application claims priority under 35 U.S.C. §119 to U.S. Provisional Application Ser. No. 60/730,206, filed Oct. 24, 2005, entitled TRANSLATING TIME-INDEPENDENT DATA USING DATABASE JOINS, the disclosure of which is incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60730206 | Oct 2005 | US |
