Method and mechanism for supporting virtual content in performing file operations at a RDBMS

• US 8,224,837 B2
• Filed: 06/29/2005
• Issued: 07/17/2012
• Est. Priority Date: 06/29/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jain, Namit, Agarwal, Nipun, Kapoor, Vikram, Pannala, Syam, Murthy, Ravi
• Primary Examiner(s): To, Baoquoc N
• Application Number:
  US11/172,088
• Publication Number:
  US 20070005555A1
• Time in Patent Office: 2,575 Days
• Field of Search: 707/1, 707/999.1, 707/831, 707/763
• US Class Current: 707/763
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: G06F 16/188 Virtual file systems

Abstract

Techniques are provided for accessing and storing files within a virtual folder. A virtual folder is a folder that is logically a part of a hierarchical folder structure of a file system repository, but the contents of the virtual folder are not physically stored in the file system repository. A client may issue, to an access mechanism, a request to perform a file operation on a file in a virtual folder. The access mechanism, which may be a database server or a component therein, may perform the file operation on the file in the virtual folder as if the file was stored in a particular folder within the hierarchical folder structure implemented by the file system repository. Advantageously, files may be physically stored outside of the file system repository, but still be a part of the hierarchical folder structure implemented by the file system repository.

Claims

1. A machine-implemented method for providing access to one or more files:

wherein the method is performed by one or more computing devices implementing an SQL-supporting database server that processes SQL commands and commands that conform to a file system protocol to store a plurality of files in folders within a hierarchical folder structure implemented by a repository;

wherein the method comprises;

receiving a file system command at the SQL-supporting database server, wherein the file system command conforms to the file system protocol, wherein the command references a file as if said file were stored in a particular folder within the hierarchical folder structure that is implemented by said repository;

determining whether the file is stored in said repository;

in response to determining that the file is not stored in the repository, the SQL-supporting database server responding to the file system command by accessing information associated with said file, said information being located in a location other than said repository;

wherein said repository is stored in a relational database managed by the SQL-supporting database server.

2. The method of claim 1, further comprising:

obtaining an identifier that uniquely identifies the file relative to the location; and

generating a filehandle for said file based, at least in part, on the identifier;

wherein the identifier is different than the filehandle.

3. The method of claim 2, wherein said step of obtaining an identifier is performed by accessing information, maintained by a database that is implementing said repository, identifying items stored in said database.

4. The method of claim 2, wherein the filehandle includes a flag indicating that the file is not in the repository and data indicating a virtual folder in said hierarchical structure at which the file is deemed to be located.

5. The method of claim 1, further comprising:

storing, in association with an identifier for the file, data indicating a callback function to an external entity responsible for providing access to said file at the location, wherein execution of said callback function by the external entity causes the external entity to perform an operation with respect to the file;

wherein the SQL-supporting database server accessing information associated with said file comprises the SQL-supporting database server looking up the callback function using at least the identifier, and, upon locating the callback function, sending the callback function to the external entity.

6. The method of claim 5, wherein the callback function, when executed by the external entity, causes the external entity to retrieve the file using an identifier that uniquely identifies the file relative to the location.

7. The method of claim 1, further comprising:

receiving a second file system command at the SQL-supporting database server, wherein the second file system command requests to create a virtual folder, within said hierarchical folder structure;

in response to the second file system command, storing data for the virtual folder, said data indicating one or more callback functions to an external entity responsible for providing access, at the location, to information associated with one or more files indicated by the repository as being within the virtual folder, wherein the one or more files include the file.

8. The method of claim 7, further comprising receiving data indicating said one or more callback functions from a user.

9. The method of claim 1, further comprising:

the database server performing a lock operation on the file, wherein the lock operation is performed using a same lock mechanism that is used for locking files stored within said repository.

10. The method of claim 1, further comprising:

the database server performing a security operation on the file, wherein the security operation is performed using a same security mechanism that is used for performing security operations on files stored within said repository.

11. The method of claim 1, wherein the location other than said repository is a file system external to the relational database.

12. The method of claim 1, wherein the file system command is a first file system command and the file is a first file, the method further comprising:

receiving a second file system command at the SQL-supporting database server, wherein the command references a second file as if said second file were stored in a second folder within the hierarchical folder structure that is implemented by said repository;

determining whether the second file is stored in said repository; and

in response to determining that the second file is stored in the repository, the SQL-supporting database server responding to the file system command by reading information associated with said second file from the relational database.

13. The method of claim 1 wherein the file system protocol is Network File System (NFS).

14. A volatile or non-volatile storage storing one or more sequences of instructions for providing access to one or more files, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

implementing an SQL-supporting database server that processes SQL commands and commands that conform to a file system protocol to store a plurality of files in folders within a hierarchical folder structure implemented by a repository;

receiving a file system command at the SQL-supporting database server, wherein the file system command conforms to the file system protocol, wherein the command references a file as if said file were stored in a particular folder within the hierarchical folder structure that is implemented by said repository;

determining whether the file is stored in said repository;

in response to determining that the file is not stored in the repository, the SQL-supporting database server responding to the file system command by accessing information associated with said file, said information being located in a location other than said repository;

wherein said repository is stored in a relational database managed by the SQL-supporting database server.

15. The volatile or non-volatile storage of claim 14, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the steps of:

obtaining an identifier that uniquely identifies the file relative to the location; and

generating a filehandle for said file based, at least in part, on the identifier;

wherein the identifier is different than the filehandle.

16. The volatile or non-volatile storage of claim 15, wherein said step of obtaining an identifier is performed by accessing information, maintained by a database that is implementing said repository, identifying items stored in said database.

17. The volatile or non-volatile storage of claim 15, wherein the filehandle includes a flag indicating that the file is not in the repository and data indicating a virtual folder in said hierarchical structure at which the file is deemed to be located.

18. The volatile or non-volatile storage of claim 14, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the step of:

storing, in association with an identifier for the file, data indicating a callback function to an external entity responsible for providing access to said file at the location, wherein execution of said callback function by the external entity causes the external entity to perform an operation with respect to the file;

wherein the SQL-supporting database server accessing information associated with said file comprises the SQL-supporting database server looking up the callback function using at least the identifier, and, upon locating the callback function, sending the callback function to the external entity.

19. The volatile or non-volatile storage of claim 18, wherein the callback function, when executed by the external entity, causes the external entity to retrieve the file using an identifier that uniquely identifies the file relative to the location.

20. The volatile or non-volatile storage of claim 14, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the step of:

receiving a second file system command at the SQL-supporting database server, wherein the second file system command requests to create a virtual folder, within said hierarchical folder structure;

in response to the second file system command, storing data for the virtual folder, said data indicating one or more callback functions to an external entity responsible for providing access, at the location, to information associated with one or more files indicated by the repository as being within the virtual folder, wherein the one or more files include the file.

21. The volatile or non-volatile storage of claim 20, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the step of receiving data indicating said one or more callback functions from a user.

22. The volatile or non-volatile storage of claim 14, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the step of:

the database server performing a lock operation on the file, wherein the lock operation is performed using a same lock mechanism that is used for locking files stored within said repository.

23. The volatile or non-volatile storage of claim 14, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the step of:

the database server performing a security operation on the file, wherein the security operation is performed using a same security mechanism that is used for performing security operations on files stored within said repository.

24. The volatile or non-volatile storage of claim 14, wherein the location other than said repository is a file system external to the relational database.

25. The volatile or non-volatile storage of claim 14, wherein the file system command is a first file system command and the file is a first file, wherein execution of the one or more sequences of instructions by the one or more processors further causes the one or more processors to perform the steps of:

receiving a second file system command at the SQL-supporting database server, wherein the command references a second file as if said second file were stored in a second folder within the hierarchical folder structure that is implemented by said repository;

determining whether the second file is stored in said repository; and

in response to determining that the second file is stored in the repository, the SQL-supporting database server responding to the second file system command by reading information associated with said second file from the relational database.

26. The volatile or non-volatile storage of claim 14, wherein the file system protocol is NFS.