CN111881087A - File management operation method and related device - Google Patents
File management operation method and related device Download PDFInfo
- Publication number
- CN111881087A CN111881087A CN202010752552.3A CN202010752552A CN111881087A CN 111881087 A CN111881087 A CN 111881087A CN 202010752552 A CN202010752552 A CN 202010752552A CN 111881087 A CN111881087 A CN 111881087A
- Authority
- CN
- China
- Prior art keywords
- accessory
- storage table
- file
- attachment
- management operation
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000004590 computer program Methods 0.000 claims description 11
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 58
- 230000006870 function Effects 0.000 description 14
- 238000005516 engineering process Methods 0.000 description 4
- 238000013523 data management Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000011017 operating method Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1737—Details of further file system functions for reducing power consumption or coping with limited storage space, e.g. in mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a file management operation method, which comprises the following steps: inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table; when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table; and executing file management operation according to the file storage table associated with the attachment storage table. Management operation is performed on the corresponding files through the associated file storage tables, so that the files are prevented from being independently set in corresponding areas, association is only needed, and the flexibility of using file data is improved. The application also discloses a file management operating device, a server and a computer readable storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a file management operation method, a file management operation device, a server, and a computer-readable storage medium.
Background
With the continuous development of information technology, the functions used in the information technology are more and more abundant, and the corresponding generated data is more and more, so that the corresponding management operation needs to be performed on more and more data.
In the related art, a file management system generally performs a corresponding management operation on file data. However, a file management system is generally provided for each function, and is dedicated to managing file data corresponding to the function. Finally, each function manages and uses its own file data, which may cause duplicate file data, and may lead to file data management not being flexible and timely. In addition, the storage space is wasted, and the space utilization rate is reduced.
Therefore, how to improve the flexibility of using file data by different functions is a key issue of attention of those skilled in the art.
Disclosure of Invention
The file management operation method, the file management operation device, the server and the computer readable storage medium are provided, and through the acquired attachment storage table associating the business agent ID with the file storage table, management operation is executed on the corresponding file according to the associated file storage table, so that the file is prevented from being independently set in a corresponding area, only association is needed, and the flexibility of using file data is improved.
In order to solve the above technical problem, the present application provides a file management operation method, including:
inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table;
when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table;
and executing file management operation according to the file storage table associated with the attachment storage table.
Optionally, querying a corresponding accessory storage table according to the received service agent ID and the received accessory ID includes:
inquiring an accessory storage table according to the received service main body ID to obtain an accessory storage table corresponding to the service main body ID;
and inquiring in an accessory storage table corresponding to the service main body ID according to the accessory ID.
Optionally, when the accessory storage table is not queried, querying an accessory configuration table corresponding to the accessory ID, and initializing according to the accessory configuration table and the service agent ID to obtain the accessory storage table, where the method includes:
when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID;
copying data of the accessory configuration table into an initial accessory storage table;
and updating the service body ID to a corresponding field of the initial accessory storage table to obtain the accessory storage table.
Optionally, the executing the file management operation according to the file storage table associated with the attachment storage table includes:
when the management operation is information viewing, acquiring information of all file storage tables associated with the attachment storage table to obtain a plurality of file information;
and sending the file information to service equipment.
Optionally, the executing the file management operation according to the file storage table associated with the attachment storage table includes:
when the management operation is file uploading, inserting information of a file to be uploaded into a file storage table associated with the attachment storage table;
and generating the file ID of the file to be uploaded, and writing the file ID into a corresponding file storage table.
The present application further provides a file management operating apparatus, including:
the related information inquiry module is used for inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table;
the association information initialization module is used for inquiring the accessory configuration table corresponding to the accessory ID when the accessory storage table is not inquired, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table;
and the file operation module is used for executing file management operation according to the file storage table associated with the attachment storage table.
Optionally, the associated information query module includes:
a service agent ID query unit, configured to perform an accessory storage table query according to the received service agent ID, to obtain an accessory storage table corresponding to the service agent ID;
and the accessory ID query unit is used for querying an accessory storage table corresponding to the service main body ID according to the accessory ID.
Optionally, the association information initializing module includes:
a configuration table obtaining unit, configured to, when the accessory storage table is not queried, query an accessory configuration table corresponding to the accessory ID;
the data copying unit is used for copying the data of the accessory configuration table into an initial accessory storage table;
and the ID updating unit is used for updating the service main body ID to a corresponding field of the initial accessory storage table to obtain the accessory storage table.
The present application further provides a server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the file management operation method as described above when executing the computer program.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the file management operating method as described above.
The application provides a file management operation method, which comprises the following steps: inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table; when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table; and executing file management operation according to the file storage table associated with the attachment storage table.
Through the acquired accessory storage table associating the business body ID with the file storage table, the accessory storage table is initialized when the accessory storage table does not exist, then management operation is performed on the corresponding file according to the associated file storage table, the situation that the file is set in a corresponding area independently is avoided, only association is needed, the flexibility degree of using the file data is improved, meanwhile, the same file data can be used by a plurality of business functions, the use efficiency of the file data is improved, and the storage space is saved.
The application further provides a file management operating device, a server and a computer readable storage medium, which have the above beneficial effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a file management operation method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a file management operating device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a file management operation method, a file management operation device, a server and a computer readable storage medium, through obtaining an accessory storage table associating a business agent ID with a file storage table, and then executing management operation on a corresponding file according to the associated file storage table, avoiding setting a corresponding area for the file independently, and improving the flexibility of using file data as long as association is needed.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the related art, a file management system generally performs a corresponding management operation on file data. However, a file management system is generally provided for each function, and is dedicated to managing file data corresponding to the function. Finally, each function manages and uses its own file data, which may cause duplicate file data, and may lead to file data management not being flexible and timely. In addition, the storage space is wasted, and the space utilization rate is reduced.
Therefore, the file management operation method provided by the application initializes the accessory storage table when the accessory storage table does not exist through the acquired accessory storage table associating the service main body ID with the file storage table, and then executes management operation on the corresponding file according to the associated file storage table, so that the situation that the file is set in a corresponding area independently is avoided, only association is needed, the flexibility degree of using the file data is improved, meanwhile, a plurality of service functions can also use the same file data, the use efficiency of the file data is improved, and the storage space is saved.
The following describes a file management operation method provided by the present application, with an embodiment.
Referring to fig. 1, fig. 1 is a flowchart illustrating a file management operation method according to an embodiment of the present disclosure.
In this embodiment, the method may include:
s101, inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service main body ID with the file storage table;
this step is intended to inquire whether there is a corresponding attachment storage table according to the identity identification number (ID) of the service agent and the ID of the attachment when the service agent issues a file. The query result of the query may be that the corresponding attachment storage table exists, or that the corresponding attachment storage table does not exist.
The attachment in this embodiment is a basic unit for managing files, and the attachment only stores files and cannot store subfolders. In this embodiment, the service agent performs corresponding operation and management on the file through the attachment.
The attachment storage table is used for storing attachment data associated with actual services. Its role is to store two key attributes of a file, namely a business body ID and an attachment name (attachment ID, used to associate an attachment configuration table and obtain the attachment name).
It can be seen that a complete accessory storage table records the service body ID and the accessory ID. Therefore, when the available accessory storage table is queried, the corresponding query operation can be performed through the service body ID and the accessory ID.
Optionally, this embodiment may include:
step 1, inquiring an accessory storage table according to a received service main body ID to obtain an accessory storage table corresponding to the service main body ID;
and 2, inquiring in an accessory storage table corresponding to the service body ID according to the accessory ID.
It can be seen that the present alternative is mainly described how to perform the accessory storage table lookup. Specifically, in this alternative, first, an accessory storage table is queried according to the received service agent ID, so as to obtain an accessory storage table corresponding to the service agent ID. That is, a table is searched for all attachments corresponding to the service agent ID. Then, according to the accessory ID, inquiring in an accessory storage table corresponding to the service main body ID. That is, the accessory storage table corresponding to the accessory ID is found out from all the accessory storage tables corresponding to the service agent ID. Obviously, in this alternative scheme, the main step is to search the service agent ID first and then search the accessory ID, so as to determine the corresponding accessory storage table.
S102, when the accessory storage table cannot be inquired, inquiring an accessory configuration table corresponding to an accessory ID, and initializing according to the accessory configuration table and a service body ID to obtain an accessory storage table;
on the basis of S101, this step aims to construct a corresponding accessory storage table in an initialization manner when the accessory storage table is not queried. Specifically, an accessory configuration table corresponding to the accessory ID is queried, and initialization is performed according to the accessory configuration table and the service agent ID to obtain an accessory storage table.
The main purpose is to associate the service body ID and the accessory ID, that is, to store the information of the two in a new accessory storage table. Specifically, the operation process may refer to the following alternatives.
Optionally, this step may include:
step 1, when the accessory storage table cannot be inquired, inquiring an accessory configuration table corresponding to an accessory ID;
step 2, copying the data of the accessory configuration table to an initial accessory storage table;
and 3, updating the service body ID to a corresponding field of the initial accessory storage table to obtain an accessory storage table.
It can be seen that the present alternative is mainly described how to initialize the accessory storage table. In this alternative, when the accessory storage table is not queried, the accessory configuration table corresponding to the accessory ID is queried first. That is, the accessory configuration table corresponding to the accessory ID is found, that is, the corresponding accessory already exists in the server, and when the accessory needs to be used in this embodiment, it is not necessary to duplicate the file data in the accessory and associate the accessory with the service main body. For an already existing accessory, there is a corresponding accessory configuration table. The data of the accessory configuration table is copied to the initial accessory storage table. I.e., the data in the attachment configuration table is copied to the initial attachment storage table. And finally, updating the service body ID to a corresponding field of the initial accessory storage table to obtain an accessory storage table.
S103, file management operation is executed according to the file storage table associated with the attachment storage table.
On the basis of S102 or S101, that is, on the basis of the technology in which the attachment storage table already exists, the corresponding file management operation is performed through the file storage table corresponding to the attachment storage table. The attachment storage table indicates that the business body is associated with the corresponding attachment or file data, and the file data can be directly operated through the associated information without copying the corresponding file data to the business body for operation.
Optionally, this step may include:
step 1, when the management operation is information viewing, acquiring information of all file storage tables associated with an attachment storage table to obtain a plurality of file information;
and step 2, sending the plurality of file information to the service equipment.
It can be seen that this alternative is primarily illustrative of the file management operations that are performed. In this alternative, when the management operation is to view information, first, information of all file storage tables associated with the attachment storage table is acquired to obtain a plurality of pieces of file information. And then, transmitting the plurality of file information to the service equipment. That is, only the file information of all the files is obtained, the file information of the corresponding files can be obtained through the corresponding file storage table, and finally all the file information is sent to the service device.
Optionally, this step may include:
step 1, when the management operation is file uploading, inserting information of a file to be uploaded into a file storage table associated with an attachment storage table;
and 2, generating a file ID of the file to be uploaded, and writing the file ID into a corresponding file storage table.
It can be seen that this alternative is primarily illustrative of the file management operations that are performed. In the alternative, when the management operation is file uploading, inserting the information of the file to be uploaded into a file storage table associated with the attachment storage table; and generating a file ID of the file to be uploaded, and writing the file ID into a corresponding file storage table. That is, when a file is uploaded, the file data may be associated with the corresponding attachment storage table.
In addition, the method can also comprise the step of executing deletion operation on the file. Specifically, the corresponding file information in the file storage table may be deleted according to the file ID in the deletion request.
In summary, in the embodiment, the obtained attachment storage table associating the service agent ID with the file storage table is used to initialize the attachment storage table when the attachment storage table does not exist, and then the management operation is performed on the corresponding file according to the associated file storage table, so that the situation that the file is set up in a corresponding area alone is avoided, and only association is required, so that the flexibility of using the file data is improved, and meanwhile, a plurality of service functions can also use the same file data, so that the use efficiency of the file data is improved, and the storage space is saved.
A file management operation method provided in the present application is further described below with reference to a specific embodiment.
First, the data table used in the embodiment will be described in this embodiment.
The attachment configuration table (t _ config _ item) is used for configuring information of an attachment, and the design of each field fully considers various service scenes and various customization needs.
The fields in this table are set as follows:
1) the format field specifies the file format that the attachment is allowed to upload. For example, some services can only upload a picture format, some services can only upload a pdf format, and the like;
2) the max _ size field specifies the maximum file size that the attachment is allowed to upload. If the video attachment is found, the uploaded file may be allowed to be large; if it is a picture file, the uploaded file may be allowed to be small;
3) the max _ num field specifies the maximum number of files that the attachment is allowed to upload. For example, only two identity card photos need to be uploaded at most.
Wherein, the attachment storage table (t _ file _ item) is used for storing attachment data associated with the actual service. The role of the method is to store two key attributes of a file, namely, a business body (business _ id) and an attachment name (i.e., item _ id, which is used for associating a t _ config _ item table and obtaining the attachment name).
The fields in this table are set as follows:
1) business _ id: a service ID for uniquely marking a service body. Such as a customer ID, an item ID, etc.;
2) item _ id: an accessory ID for marking a specific accessory. Through this field, it can be directly associated to the attachment configuration table (t _ config _ item) for obtaining the name of the attachment;
3) format, max _ size, max _ num: the values of the three fields are copied from the attachment configuration table t _ config _ item table by default, and when the special service scene is encountered, the values of the three attributes can be modified to realize personalized configuration. For example, in general, the identity card photos of the client are two pieces of front and back, if a overseas client is encountered, passport information needs to be uploaded, and the value of max _ num in the t _ file _ item table can be modified for the client.
The file storage table (t _ file _ item _ files) is used for storing specific file information. Because the attachment and the file are managed in one-to-many mode, a plurality of files can be uploaded under the attachment of one business body, and therefore a table needs to be maintained independently.
1) The file _ item _ id field is used to associate a unique entry in the attachment storage table. The one-to-many relationship of the attachment and the file is realized based on this field.
2) The file _ name, file _ format, and file _ size may be automatically retrieved to values when uploading a file.
3) And location for recording the storage position of the file. Since file storage locations of different companies or different projects are different, for example, some companies store files on a local server, and some companies store files on a cloud server, where and how the files are stored are not in the range related to this embodiment.
On the basis of the above data table, the file management operation in the present embodiment may include:
the first step is as follows: the data in the attachment storage table (t _ file _ item) is queried or initialized. Inquiring an attachment storage table (t _ file _ item) according to the service body ID (corresponding to the business _ ID field in the t _ file _ item table) and the attachment ID (corresponding to the item _ ID field in the t _ file _ item table), and if records exist, indicating that initialization is already performed; if the data is not recorded, inquiring the accessory configuration table (t _ config _ item) according to the accessory ID (corresponding to the ID field in the t _ config _ item table), copying the inquired data into the accessory storage table (t _ file _ item), and updating the newly added business _ ID field value in the t _ file _ item table into the service body ID.
The second step is that: and inquiring the file storage table (t _ file _ item _ files) according to the ID of the attachment storage table inquired in the first step to obtain all files (including the ID of the file). If the service function requests an interface for viewing the file list, the file information (including the ID of the file) acquired at this step is returned to the service function.
The third step: if the file is requested to be uploaded, inserting the information of the uploaded file into a file storage table (the ID of the file is automatically generated when the file is inserted); if the file is requested to be deleted, deleting the corresponding file information in the file storage table according to the file ID requested to be deleted.
It can be seen that in this embodiment, by obtaining the accessory storage table associating the service agent ID with the file storage table, when the accessory storage table does not exist, the accessory storage table is initialized, and then the management operation is performed on the corresponding file according to the associated file storage table, so as to avoid setting up a corresponding area for the file separately, as long as the file is associated, thereby improving the flexibility of using the file data, and meanwhile, a plurality of service functions can also use the same file data, thereby improving the use efficiency of the file data, and saving the storage space.
In the following, a file management operation device provided by an embodiment of the present application is introduced, and a file management operation device described below and a file management operation method described above may be referred to in correspondence.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a file management operation device according to an embodiment of the present application.
In this embodiment, the apparatus may include:
the association information query module 100 is configured to query a corresponding accessory storage table according to the received service agent ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service main body ID with the file storage table;
the association information initialization module 200 is configured to, when the accessory storage table cannot be queried, query an accessory configuration table corresponding to an accessory ID, and initialize according to the accessory configuration table and a service agent ID to obtain an accessory storage table;
the file operation module 300 is configured to perform a file management operation according to the file storage table associated with the attachment storage table.
Optionally, the association information query module 100 may include:
the service body ID query unit is used for querying the accessory storage table according to the received service body ID to obtain an accessory storage table corresponding to the service body ID;
and the accessory ID inquiry unit is used for inquiring in an accessory storage table corresponding to the service body ID according to the accessory ID.
Optionally, the association information initialization module 200 may include:
the configuration table acquisition unit is used for inquiring the accessory configuration table corresponding to the accessory ID when the accessory storage table cannot be inquired;
the data copying unit is used for copying the data of the accessory configuration table into the initial accessory storage table;
and the ID updating unit is used for updating the service body ID to the corresponding field of the initial attachment storage table to obtain the attachment storage table.
An embodiment of the present application further provides a server, including:
a memory for storing a computer program;
a processor for implementing the steps of the file management operation method as described in the above embodiments when executing the computer program.
Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the file management operation method according to the above embodiments are implemented.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The document management operation method, the document management operation device, the server, and the computer-readable storage medium provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A file management operation method, comprising:
inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table;
when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table;
and executing file management operation according to the file storage table associated with the attachment storage table.
2. The file management operation method according to claim 1, wherein querying the corresponding attachment storage table according to the received service agent ID and the attachment ID comprises:
inquiring an accessory storage table according to the received service main body ID to obtain an accessory storage table corresponding to the service main body ID;
and inquiring in an accessory storage table corresponding to the service main body ID according to the accessory ID.
3. The file management operation method according to claim 1, wherein, when the attachment storage table is not queried, querying an attachment configuration table corresponding to the attachment ID, and initializing according to the attachment configuration table and the service agent ID to obtain the attachment storage table, comprises:
when the accessory storage table is not inquired, inquiring an accessory configuration table corresponding to the accessory ID;
copying data of the accessory configuration table into an initial accessory storage table;
and updating the service body ID to a corresponding field of the initial accessory storage table to obtain the accessory storage table.
4. The file management operation method according to claim 1, wherein performing a file management operation according to a file storage table associated with the attachment storage table comprises:
when the management operation is information viewing, acquiring information of all file storage tables associated with the attachment storage table to obtain a plurality of file information;
and sending the file information to service equipment.
5. The file management operation method according to claim 1, wherein performing a file management operation according to a file storage table associated with the attachment storage table comprises:
when the management operation is file uploading, inserting information of a file to be uploaded into a file storage table associated with the attachment storage table;
and generating the file ID of the file to be uploaded, and writing the file ID into a corresponding file storage table.
6. A file management operation apparatus, characterized by comprising:
the related information inquiry module is used for inquiring a corresponding accessory storage table according to the received service main body ID and the received accessory ID; wherein, the attachment storage table is obtained by associating the service body ID with the file storage table;
the association information initialization module is used for inquiring the accessory configuration table corresponding to the accessory ID when the accessory storage table is not inquired, and initializing according to the accessory configuration table and the service body ID to obtain the accessory storage table;
and the file operation module is used for executing file management operation according to the file storage table associated with the attachment storage table.
7. The file management operation device according to claim 6, wherein the association information query module includes:
a service agent ID query unit, configured to perform an accessory storage table query according to the received service agent ID, to obtain an accessory storage table corresponding to the service agent ID;
and the accessory ID query unit is used for querying an accessory storage table corresponding to the service main body ID according to the accessory ID.
8. The file management operation device according to claim 6, wherein the association information initialization module includes:
a configuration table obtaining unit, configured to, when the accessory storage table is not queried, query an accessory configuration table corresponding to the accessory ID;
the data copying unit is used for copying the data of the accessory configuration table into an initial accessory storage table;
and the ID updating unit is used for updating the service main body ID to a corresponding field of the initial accessory storage table to obtain the accessory storage table.
9. A server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the file management operation method according to any one of claims 1 to 5 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the file management operation method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010752552.3A CN111881087A (en) | 2020-07-30 | 2020-07-30 | File management operation method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010752552.3A CN111881087A (en) | 2020-07-30 | 2020-07-30 | File management operation method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111881087A true CN111881087A (en) | 2020-11-03 |
Family
ID=73204627
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010752552.3A Pending CN111881087A (en) | 2020-07-30 | 2020-07-30 | File management operation method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111881087A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1392989A (en) * | 2000-07-24 | 2003-01-22 | 松下电器产业株式会社 | System for transmission/reception of E-mail with attached files |
| CN102067107A (en) * | 2008-06-20 | 2011-05-18 | 微软公司 | Displaying a list of file attachments associated with a message thread |
| US20110307446A1 (en) * | 2008-12-26 | 2011-12-15 | Shingo Miyazaki | Information life cycle management system, information management server apparatus, information media controlling apparatus and program |
| CN104408044A (en) * | 2014-10-23 | 2015-03-11 | 北京用友政务软件有限公司 | File access method and system |
| CN109408535A (en) * | 2018-09-28 | 2019-03-01 | 中国平安财产保险股份有限公司 | Big data quantity matching process, device, computer equipment and storage medium |
| CN110611608A (en) * | 2019-09-29 | 2019-12-24 | 武汉思普崚技术有限公司 | WEB mail auditing method and system |
| CN110609954A (en) * | 2019-08-30 | 2019-12-24 | 深圳壹账通智能科技有限公司 | Data acquisition method and device, computer equipment and storage medium |
-
2020
- 2020-07-30 CN CN202010752552.3A patent/CN111881087A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1392989A (en) * | 2000-07-24 | 2003-01-22 | 松下电器产业株式会社 | System for transmission/reception of E-mail with attached files |
| CN102067107A (en) * | 2008-06-20 | 2011-05-18 | 微软公司 | Displaying a list of file attachments associated with a message thread |
| US20110307446A1 (en) * | 2008-12-26 | 2011-12-15 | Shingo Miyazaki | Information life cycle management system, information management server apparatus, information media controlling apparatus and program |
| CN104408044A (en) * | 2014-10-23 | 2015-03-11 | 北京用友政务软件有限公司 | File access method and system |
| CN109408535A (en) * | 2018-09-28 | 2019-03-01 | 中国平安财产保险股份有限公司 | Big data quantity matching process, device, computer equipment and storage medium |
| CN110609954A (en) * | 2019-08-30 | 2019-12-24 | 深圳壹账通智能科技有限公司 | Data acquisition method and device, computer equipment and storage medium |
| CN110611608A (en) * | 2019-09-29 | 2019-12-24 | 武汉思普崚技术有限公司 | WEB mail auditing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11689515B2 (en) | Information processing device, information management method, and information processing system | |
| US11233851B2 (en) | System, method, and computer program for enabling a user to access and edit via a virtual drive objects synchronized to a plurality of synchronization clients | |
| US7664829B2 (en) | Document managing system, document managing apparatus and document managing method | |
| US7945535B2 (en) | Automatic publishing of digital content | |
| CN109739815B (en) | File processing method, system, device, equipment and storage medium | |
| US20070299880A1 (en) | Document Management Server, Document Management Method, Computer Readable Medium, Computer Data Signal, and System For Managing Document Use | |
| US20080301261A1 (en) | Data file edit system, storage medium, process server, and user client | |
| KR102032583B1 (en) | Access to supplemental data based on identifier derived from corresponding primary application data | |
| CN105704218B (en) | Data storage and management method in cloud computing platform | |
| CN105824932A (en) | Archive system for storing OSS based on Aliskiu object | |
| CN104573079A (en) | Intelligent image file uploading management method | |
| US8373876B2 (en) | Document management system and method for controlling a document print operation | |
| CN102402547A (en) | Information processing method and device | |
| CN103716488A (en) | Information processing device | |
| JP2010003127A (en) | Document management device, document management system, document management method and computer program | |
| CN111881087A (en) | File management operation method and related device | |
| EP2845090A1 (en) | Transmitting a job to a destination | |
| US10762045B2 (en) | Mounting dynamic endpoints | |
| CN113687783B (en) | Object aggregation method, system, device and computer storage medium | |
| CN115563071A (en) | Data processing method, system, electronic device and computer readable storage medium | |
| US8588851B2 (en) | Android mobile telephone comprising a content supply chain | |
| CN108566421A (en) | A kind of network type location mode and system based on Network Attached Storage | |
| JP2001036700A (en) | Image processing unit and communication terminal | |
| CN103605795A (en) | Metadata-based file storage method and device | |
| CN111953722B (en) | Synchronization method and device for terminal address book |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201103 |
|
| RJ01 | Rejection of invention patent application after publication |