Abstract: A system is provided for selecting an appropriate aggregated fact data table to use as the basis for calculating an aggregation request from a set of stored aggregated fact data tables. An estimate is established of the amount of processing time required to aggregate each of the tables. The table with the lowest estimate is then used to perform the aggregation.

Abstract: A method of joining two or more sets of data in a database is provided wherein certain dimensions in the fact data are designated as being forced dimensions, and wherein for each forced dimension, a set of entries is created in the fact data each with the same key values in all of the dimensions other than the forced dimension, and each with a different member of the set of values existing in the fact data for that dimension, if and only if at least one entry exists in the fact data with the same set of key values in the dimensions other than the forced dimension.

Abstract: In response to a constraint violation in a row of a database table, an output file is generated including the characteristics of the table containing the row in error as well as an SQL UPDATE statement for the row. The SQL UPDATE statement includes the column values in the row which can be corrected by the user, the user modified SQL UPDATE statement being subsequently executed to repair the constraint violation.

Abstract: A utility with which a programmer can generate or alter computer code for a calendaring function, and test the code prior to compilation. Entering the program in edit mode, the programmer locates a portion of the program where code for a calendaring function is to be generated or altered, and invokes the date logic generator. The date logic generator provides an initial window with a choice of calendaring functions, and upon selecting a calendaring function, a parameters window displaying a number of first-level parameters for that function is provided. Depending on the specification of the values of the first-level parameters, sub-windows with second-level parameters may be provided. And, in general, depending on the specification of the values of the n-level parameters, (n+1)-level parameters may be provided in sub-windows. The parameters provided at any instant are only those which have already been specified or those that require specification.

Abstract: A method and system for transforming and manipulating program object code. A set of program object code is transformed into a form in which it may be readily manipulated, preferably a form which is independent of both the processor and the operating system with which the object code will execute. The transformed object code is manipulated, preferably to add error-checking instructions, but possibly to add other functions or to alter the functions of the object code. The manipulated code is then reverse-transformed to program object code of the same type as the original object code.

Abstract: The invention disclosed herein is implemented in a repository which stores metadata relating to data stored in one or more databases. The repository includes a repository database in which the metadata is stored, one or more scanners each of which scans at least one database and obtains metadata therefrom, and one or more loaders each of which loads metadata obtained by at least one scanner into the repository database in accordance with the externalized reuse criteria. According to the invention, metadata stored in the repository is reused, for example, not replaced by identical metadata when the repository is updated or populated, and the criteria governing reuse is externalized, i.e., accessible and modifiable by a repository user. The reuse criteria accessible to repository users is stored separate from repository program code at a non-programming level such that the customer (user) can change the reuse procedures without an experienced programmer.

Abstract: Conversion of Gregorian calendar dates to dates of a 360-day-year calendar (i.e., a calendar having twelve months of 30 days each), and 360-day-year calendar dates to Gregorian calendar dates, are performed using a single three-column 367-entry conversion table. A search table unit searches the conversion table from the bottom upwards, i.e., a table search index is initialized to a value of 367, and decremented by unity each time a comparison is made and a match is not found. A first field in each row of the conversion table contains Gregorian leap year calendar days-of-the-year, a second field in each row contains Gregorian non-leap year calendar days-of-the-year, and a third field in each row contains 360-day-year calendar days-of-the-year. A graph of Gregorian days-of-the-year versus 360-day-year days-of-the-year has both vertical and horizontal sections.

Abstract: A calendaring system which provides accurate calendaring of all dates between Jan. 01, 0001 and Dec. 31, 9999 by implementation of an extended set of leap-year rules. The system includes a variety of additional useful features including: multiple holiday tables; flexible date formats; free form definition of processing days; full support for fiscal calendaring units; changeable endpoint counting modes; and integrated support for the current date in date calendaring calculations.