Patent Application
20050240554
This invention relates to a data storage method and to a system adapted to perform that method.
Conventional file storage systems are ubiquitous; every desktop computer is provided with a system for the storage and retrieval of data files.
More complex file storage systems are available which can offer features such as inter-file dependency tracking. Such a system may be useful for storage of, for example, Java objects but there is an inherent disadvantage with this type of system since the files being stored using it, for example, the Java objects, must be adapted to conform to a standard required by the system. This is extremely inconvenient since each stored Java class must be modified to take account of the storage system. Furthermore, it is extremely inconvenient when the user does not wish to make use of the enhanced facilities of the system since he must nevertheless adapt the file to be stored such that it is compatible with the system.
In accordance with one aspect of the present invention there is provided a data storage method comprising receiving a store command issued by a user in respect of a data object, and in response:
Hence, by ascertaining whether an auxiliary function, which may be used to implement dependency tracking or other enhanced features, is associated with the data object and executing such an associated auxiliary function, the invention provides a method whereby data objects can simply be stored if it is not desired to make use of the enhanced features or alternatively, the enhanced features may be implemented, if desired. The invention performs this function automatically thereby overcoming the problems with the prior art in which users were inconvenienced by being forced to modify data objects to conform with the enhanced data storage system even if they did not wish to make use of the enhanced facilities.
In one embodiment, the auxiliary function ascertains whether the data object is dependent upon one or more of the already stored data objects and constructs a dependency list that indicates any such dependencies.
In yet another embodiment, the auxiliary function establishes a unique identification code for the data object and stores this identification code either in the data object itself or in a separate identification code table.
In a second aspect of the invention, a data storage method comprises receiving a store command issued by a user in respect of a data object, and in response:
Thus, the invention also provides a method in which if there is no auxiliary function associated with the data object the data object is simply stored or alternatively, the auxiliary function is executed before any storage operation is performed and the data object is only stored dependent on a result generated by the auxiliary function.
The invention may be provided as a computer program comprising computer program code means adapted to perform the steps of the methods defined by the first and second aspects of the invention when said program is run on a computer.
Alternatively, the invention may be provided as a computer program product comprising program code means stored on a computer readable medium for performing the method of either of the two aspects of the invention when said program is run on a computer.
According to a third aspect of the invention, a data storage system comprises a store for storing data objects and a controller adapted to perform the method according to the first and second aspect of the invention and store the data objects in the store.
An embodiment of the invention will now be described with reference to the accompanying drawings, in which:
The invention operates by inspecting a file to be saved before it is stored on the hard disk 2. The file may be a Java object or C# object or alternatively, it may be a document file such as a word document or PDF document. If, on inspection of the file to be saved it is ascertained that no auxiliary function is associated with the file then it is simply stored on the hard disk 2.
If, on the other hand, it is ascertained that an auxiliary function is associated with the file then the auxiliary function will be executed in addition to storing the objects. It is important to realise that, in many cases, it is unimportant whether the object is stored before or after execution of the auxiliary function and that, in some other cases, the data object may only be stored dependant on a result generated by the auxiliary function.
Some examples of possible auxiliary functions, or contracts as they are also known, will now be described to clarify the operation of the invention.
Associated with this contract there is an auxiliary function that is included in the class and this function is operable to indicate to the file storage software which other data objects the Java object 5 depends upon. In this instance, it will indicate that it depends on objects 3 and 4.
The file storage software stores the objects and constructs a dependency list 6 which indicates that the join object 5 (known as EMPDEPT in this example) depends on the table objects 3 and 4 (in this instance, EMP and DEPT respectively).
There may be a further auxiliary function associated with the adapted JOIN class that is operated on deletion of either of the objects upon which object 5 is dependent, that is objects 3 and 4. On deletion of either of these objects, the file storage software analyses the dependency list 6 and will activate the second auxiliary function in the JOIN class which, for example, may either automatically delete the object 5 or notify a user that an object upon which object 5 is dependent has been deleted.
Another contract is the “validate” contract. This is used in conjunction with the dependency tracking contract already described. It ensures that the user does not specify erroneous information, for example that the particular object depends on a non-existent object or on itself.
There is one auxiliary function associated with this contract that is operable to confirm the existence of objects which an object indicates that it depends upon and to confirm that the object does not refer to itself. If the auxiliary function returns a positive result then the data object is saved otherwise the user is notified of the discrepancy.
Another contract is the “identity” contract. This has two associated auxiliary functions. Objects implementing the contract execute the first whilst being stored and this assigns a unique identification code to the object which may be generated by the software or may be input by a user. The unique identification code may be stored in the object or in a separate list.
The second auxiliary function simply retrieves this unique identification code and presents it to a user on request.
An example is shown in
A simple example of the use of the invention will now be described with reference to
In step 15, a user deletes a table referred to by the join and, as a result, in step 16, the software checks to see if anything needs the table and determines that in this case the join depends on the table. In step 17, the join is loaded into the software and the auxiliary function associated with deletion of the dependent object is executed and as a result, the join deletes itself in step 18.
It is important to note that while the present invention has been described in a context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of a particular type of signal bearing media actually used to carry out distribution. Examples of computer readable media include recordable-type media such as floppy disks, a hard disk drive, RAM and CD-ROMs as well as transmission-type media such as digital and analogue communications links.
| Number | Date | Country | Kind |
|---|---|---|---|
| 0409125.2 | Apr 2004 | GB | national |
