CN105653525B - Method and system for importing data between account sets - Google Patents
Method and system for importing data between account sets Download PDFInfo
- Publication number
- CN105653525B CN105653525B CN201410629180.XA CN201410629180A CN105653525B CN 105653525 B CN105653525 B CN 105653525B CN 201410629180 A CN201410629180 A CN 201410629180A CN 105653525 B CN105653525 B CN 105653525B
- Authority
- CN
- China
- Prior art keywords
- data
- source
- target
- account set
- data table
- 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.)
- Active
Links
Images
Abstract
The invention provides a method for importing data between account sets, which comprises the following steps: acquiring a preset data category which is selected by a user and needs to be imported into a target account set; acquiring a source data table corresponding to the data type in a source account set, and acquiring a target data table corresponding to the data type in a target account set; judging whether the data in the source data table accord with a check rule or not according to a preset sequence, and if so, importing the data in the source data table into a target data table; and if the data in the source data table does not accord with the check rule, the import fails. The correct import of each data type is completed by the import staff through the preset sequence and the check rule, the import staff does not need to record the import sequence by themselves, and the import efficiency is improved. Meanwhile, the middle template file is not required to be output in the importing process, and data can be directly imported between the two account sets, so that the method is convenient and fast. In addition, a system for importing data between account sets is also provided.
Description
Technical Field
The invention relates to the technical field of computer data processing, in particular to a method and a system for importing data between account sets.
Background
The account set is an independent and complete data set, and the data set comprises a complete set of independent and complete system control parameters, user permissions, basic files, accounting information, receipts, account table query and the like, namely an independent database. In the prior art, data is imported from one account set into another account set through an intermediate file Excel. If logging in a source account set, exporting customer file information according to the template requirement, saving the customer file information as an Excel file in a local area, logging in a target account set, entering a customer file, and importing the Excel file as an import file to realize the import of data among 2 account sets. When data import between current account cover, have the following problem that arouses that the import of data is inefficient, inconvenient between the account cover at least:
1) a large number of intermediate files are generated and are inconvenient to store.
2) Once the source account set data changes, only new Excel files can be exported and generated, and the efficiency is not high.
3) The import and export templates have strict requirements, and once the fields are added to the database, the format of the templates is inconsistent, and the templates need to be readjusted.
4) When a plurality of import data exist, the import data often have a sequential dependence relationship, import personnel are required to record an import sequence by themselves, and if the import sequence is recorded incorrectly, the import fails, so that the working efficiency is seriously influenced.
Disclosure of Invention
In view of the above, there is a need to provide a method and system for importing data between account sets efficiently and conveniently.
A method of data import between accounts sets, the method comprising:
acquiring a preset data category which is selected by a user and needs to be imported into a target account set;
acquiring a source data table corresponding to the data type in a source account set, and acquiring a target data table corresponding to the data type in a target account set;
judging whether the data in the source data table accord with a check rule or not according to a preset sequence, and if so, importing the data in the source data table into a target data table;
and if the data in the source data table does not accord with the check rule, the import fails.
In one embodiment, before the step of obtaining the preset data category which is selected by the user and needs to be imported into the target account set, the method further includes:
acquiring the name or IP address of a source account set and the name or IP address of a target account set input by a user;
acquiring login information of a source account set and login information of a target account set, which are input by a user;
logging in a source account set according to the name or IP address of the source account set and the login information of the source account set;
and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
In one embodiment, the step of determining whether the data in the source data table conforms to the verification rule according to a preset sequence includes:
judging whether data in a source data table needs to be imported into a target data table according to a preset sequence, if so, judging whether associated data of the data exist in the target data table, if so, judging that the associated data accord with a check rule, and if not, judging that the associated data do not accord with the check rule;
if the data in the source data table does not need to be imported into the target data table, no processing is performed.
In one embodiment, whether the data in the source data table accord with the check rule or not is judged according to a preset sequence, and if the data in the source data table accord with the check rule, the data in the source data table is imported into the target data table; if the data in the source data table does not accord with the check rule, the step of failed import comprises the following steps:
copying data in the source data table to a first temporary table;
judging whether the data in the first temporary table accord with a check rule or not according to a preset sequence;
if the first temporary table accords with the verification rule, importing the data in the first temporary table into a target data table;
and if the data in the source data table does not accord with the check rule, acquiring the data failed to be imported in the first temporary table, copying the data failed to be imported to the second temporary table, and deleting the first temporary table.
In one embodiment, the method further comprises:
outputting prompt information, wherein the prompt information comprises the number of data which are successfully imported, the number of data which are failed to be imported and the reason of data import failure in the first temporary table;
and adjusting the data in the source data table or the target data table according to the reason of the data import failure, and re-importing the data in the source data table.
In one embodiment, the data in the source data table or the target data table is adjusted according to the reason of the data import failure, and the step of re-importing the data in the source data table includes:
copying data in the source data table to a first temporary table;
if the data in the first temporary table exists in the second temporary table, importing the data into a target data table;
if the data in the first temporary table is not present in the second temporary table, no processing is performed.
A system for data import between accounts sets, the system comprising:
the data type acquisition module is used for acquiring a preset data type which is selected by a user and needs to be imported into the target account set;
the data table acquisition module is used for acquiring a source data table corresponding to the data type from a source account set and acquiring a target data table corresponding to the data type from a target account set;
the data import module is used for judging whether the data in the source data table accord with the check rule or not according to a preset sequence, and importing the data in the source data table into the target data table if the data in the source data table accord with the check rule; and if the data in the source data table does not accord with the check rule, the import fails.
In one embodiment, the system further comprises a login module, configured to obtain a name or an IP address of a source account set and a name or an IP address of a target account set, which are input by a user; acquiring login information of a source account set and login information of a target account set, which are input by a user; logging in a source account set according to the name or IP address of the source account set and the login information of the source account set; and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
In one embodiment, the data import module is further configured to determine, according to a preset sequence, whether data in the source data table needs to be imported into the target data table, if so, determine whether associated data of the data exists in the target data table, if so, determine that the associated data conforms to the check rule, and if not, determine that the associated data does not conform to the check rule; if the data in the source data table does not need to be imported into the target data table, no processing is performed.
In one embodiment, the data import module comprises:
the copying unit is used for copying the data in the source data table to the first temporary table;
the checking unit is used for judging whether the data in the first temporary table accord with the checking rule or not according to a preset sequence;
the temporary table importing unit is used for importing the data in the first temporary table into the target data table if the data in the first temporary table accords with the verification rule;
and the processing unit is used for acquiring the data failed to be imported in the first temporary table if the data in the first temporary table does not accord with the check rule, copying the data failed to be imported to the second temporary table, and deleting the first temporary table.
In one embodiment, the system further comprises:
the information prompt module is used for outputting prompt information, wherein the prompt information comprises the number of data which are successfully imported into the first temporary table, the number of data which are failed to be imported and the reason of data import failure;
the re-import module is used for adjusting the data in the source data table or the target data table according to the reason of the data import failure and re-importing the data in the source data table;
in one embodiment, the re-import module is further configured to copy the data in the source data table into the first temporary table; if the data in the first temporary table exists in the second temporary table, importing the data into a target data table; if the data in the first temporary table is not present in the second temporary table, no processing is performed.
According to the method and the system for importing the data between the account sets, a source data table and a target data table corresponding to data types are respectively obtained from a source account set and a target account set by obtaining the preset data types which are selected by a user and need to be imported into the target account set; and verifying according to a preset sequence and importing the data in the source data table which accords with the verification rule into the target data table. The correct import of each data type is completed by the import staff through the preset sequence and the check rule, the import staff does not need to record the import sequence by themselves, and the import efficiency is improved. Meanwhile, the middle template file is not required to be output in the importing process, and data can be directly imported between the two account sets, so that the method is convenient and fast.
Drawings
FIG. 1 is a flow diagram of a method for data import between ledgers in one embodiment;
FIG. 2 is an illustration of an interface for data import between ledger sheets, in accordance with an embodiment;
FIG. 3 is a flowchart illustrating determining whether data in a source data table meets a check rule according to a predetermined sequence in one embodiment;
fig. 4 is a flowchart of a method of data import between ledger sheets in another embodiment;
FIG. 5 is a flowchart illustrating adjusting data in a source data table or a destination data table according to a reason for a data import failure and re-importing data in the source data table in one embodiment;
FIG. 6 is a block diagram of a system for data import between ledger sheets, in one embodiment;
FIG. 7 is a block diagram that illustrates the structure of a data import module in one embodiment;
fig. 8 is a block diagram of a system for data import between ledger sheets in another embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In one embodiment, as shown in fig. 1, there is provided a method for importing data between accounts sets, the method being applicable to a system implemented by a computer program, the method including:
step S110, acquiring a preset data category selected by the user and needing to be imported into the target account book.
In this embodiment, the preset data category may include a measurement unit, a currency, a material, a customer, a supplier, a department, an employee, and the like. Each data category corresponds to one data table in the source account set and the target account set respectively, and data related to the data category are stored in the data tables. The user can freely select the preset data category needing to be imported into the target account set according to the requirement, and can select one or more data categories. An interface can be provided for a user to select the preset data category, and the preset data category which is selected by the user and needs to be imported into the target account book is received through the interface.
Step S120, a source data table corresponding to the data category is acquired in the source account set, and a target data table corresponding to the data category is acquired in the target account set.
In this embodiment, for example, if the user selects the data category of the material, there is a source data table corresponding to the material in the source account set, as shown in table 1, the source data table includes material no, Name, and Number3 fields, and field values 001, computer, and 50 corresponding to the 3 fields, respectively. There is also a target data table corresponding to the material in the target account set, as shown in table 2, the target data table includes 3 fields of material no, Name, Number, and field values 002, pen, 65 corresponding to the 3 fields, respectively. It will be understood that the source data table and the target data table may contain the same fields, and the meaning represented by each field, such as material no representing the code of the material, Name representing the Name of the material, and Number representing the Number of the material, may be customized.
TABLE 1
| MaterialNo | 001 |
| Name | computer |
| Number | 50 |
TABLE 2
| MaterialNo | 002 |
| Name | pen |
| Number | 65 |
Step S130, determining whether the data in the source data table conforms to the check rule according to a preset sequence, if so, entering step S140, and if not, failing to import.
In this embodiment, if the user selects multiple data categories, a sequential dependency relationship may exist between data in the data tables corresponding to the multiple data categories, for example, the user selects two data categories, namely a measurement unit and a material, a field in the data table corresponding to the material is the number of the material, and the field depends on a field, namely a station, in the data table corresponding to the measurement unit, so that the data in the data table corresponding to the measurement unit needs to be imported when importing the data. According to the method and the system, the import sequence does not need to be recorded by an importer, but the system processes the data of the source data table according to the preset correct sequence according to the selection of a user, for example, whether the data in the source data table corresponding to the metering unit meets the check rule is judged firstly, and if so, the data is imported firstly.
Further, the check rule may also be self-defined, for example, if a field name and a field value in the source data table and the target data table are defined to be the same at the same time, the data is data that does not need to be imported. Or a plurality of field names and field values are defined to be the same at the same time, the data which does not need to be imported is defined.
Step S140, importing the data in the source data table into the target data table.
In this embodiment, a manner of importing the data in the source data table into the target data table may be customized, for example, whether the data in the source data table is imported into the target data table in an overlay manner or imported into the target data table in an insertion manner is selected according to a certain rule. For example, the data in the source data table is table 1, and the data in the destination data table is table 2. Defining the materialNo as a key field, and if the key fields are different, importing the key field in an insertion mode. The data in the source data table 1 is imported into the target data table 2, and the target data table is shown in table 3.
TABLE 3
| MaterialNo | 001 |
| Name | computer |
| Number | 50 |
| MaterialNo | 002 |
| Name | pen |
| Number | 65 |
If the data in the source data table is table 4, the data in the destination data table is table 5. Defining the materialNo as a key field, and if the key fields are the same, importing in an overlaying mode. The data in the source data table 4 is imported into the target data table 5, and the target data table is shown in table 6.
TABLE 4
| MaterialNo | 001 |
| Name | computer |
| Number | 50 |
TABLE 5
| MaterialNo | 001 |
| Name | computer |
| Number | 65 |
TABLE 6
| MaterialNo | 001 |
| Name | computer |
| Number | 50 |
In the embodiment, a source data table and a target data table corresponding to data types are respectively acquired in a source account set and a target account set according to preset data types which need to be imported into the target account set and are selected by a user; and importing the data in the source data table into the target data table according to a preset sequence and a check rule. The correct import of each data type is completed by the import staff through the preset sequence and the check rule, the import staff does not need to record the import sequence by themselves, and the import efficiency is improved. Meanwhile, in the importing process, the output of a middle template file is not needed, the change of an importing template is not needed to be maintained, the importing of data is directly completed between the two account sets, and the method is convenient and fast.
In one embodiment, before step S110, the method further includes: acquiring the name or IP address of a source account set and the name or IP address of a target account set input by a user; acquiring login information of a source account set and login information of a target account set, which are input by a user; logging in a source account set according to the name or IP address of the source account set and the login information of the source account set; and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
In this embodiment, the user may complete the input of the source account set and target account set names or IP addresses, the input of the user name and password of the source account set, and the input of the user name and password of the target account set through the interface shown in fig. 2. After the information is received through the interface, the source account set is logged in according to the name or the IP address of the source account set and the user name and the password of the source account set, and the target account set is logged in according to the name or the IP address of the target account set and the user name and the password of the target account set. It will be appreciated that the source and target account sets may be on the same database server, but must be two database instances. The IP addresses may be the same or different. The user name and password are not specifically required, so long as the user has the authority. The interface shown in fig. 2 also has preset data categories for the user to select, and each data category corresponds to one data table in the source account set and the target account set respectively. The interface is also provided with a shortcut key which can be used for quickly selecting and clearing all accounts, and a user can click an import key to import data of the account suite after inputting all information. Such as import between the Material table materials of database DB2013 and the Material table materials of database DB 2014.
In the embodiment, the login, the data type selection and the import key are designed in one operation interface, and all import works can be completed in one operation interface, so that the working efficiency of a user is improved.
In one embodiment, as shown in fig. 3, step S130 includes:
step S131, determining whether the data in the source data table needs to be imported into the target data table according to a preset sequence, if so, entering step S132, and if not, not performing processing.
In this embodiment, because a sequential dependency relationship may exist when importing data in the source data table, for example, the precondition for importing data B is that data a needs to be imported first, and the preset order is determined according to the dependency relationship. The judgment rule of whether the target data table needs to be imported can also be customized, for example, the material no is defined uniquely, if the material no of the material a in the source data table is 001 and the material no of the material B in the target data table is 001, the system considers that the two materials are the same, and if the two materials do not need to be imported, the two materials are not processed.
Step S132, determining whether the associated data of the data exists in the target data table, if so, determining that the associated data conforms to the verification rule, and if not, determining that the associated data does not conform to the verification rule.
In this embodiment, the associated data of the data refers to dependent data that needs to be imported into the target data table before data import. It can be understood that the data a, on which the data B to be imported in the source data table depends, may exist in the source data table, in which case we only need to import the data a first to ensure that the data B is imported into the target data table. However, if the data a on which the data B depends is not in the source data table, it is necessary to determine whether the data a on which the data B depends already exists in the target data table. If the verification rule is not met, the verification rule is judged to be met.
In another embodiment, as shown in fig. 4, there is provided a method for data import between ledgers, the method comprising:
step S210, acquiring a preset data category selected by the user and needing to be imported into the target account book.
Step S220, a source data table corresponding to the data category is obtained in the source account set, and a target data table corresponding to the data category is obtained in the target account set.
In step S230, the data in the source data table is copied to the first temporary table.
Specifically, a first temporary table is newly established in the database, and the data in the source data table is copied to the first temporary table. When a plurality of data types exist, a plurality of source data tables corresponding to the data types are possible, and for the convenience of searching, the data in the source data tables are all copied to the first temporary table, so that the importing efficiency can be improved.
Step S240, judging whether the data in the first temporary table accords with a check rule according to a preset sequence, and if so, entering step S250; if the data in the source data table does not conform to the check rule, the process proceeds to step S260.
In this embodiment, it is directly determined from the first temporary table according to the order of the front-back dependency relationship of the imported data whether each data meets the check rule, if yes, the process proceeds to step S250, and if not, the process proceeds to step S260. The data meeting the check rule is the data which needs to be imported into the target data table and meets the import condition.
Step S250, importing the data in the first temporary table into a target data table;
specifically, the data in the first temporary table, which meets the check rule, is imported into the target data table in a self-defined import mode.
Step S260, acquiring the data failed to be imported from the first temporary table, copying the data failed to be imported to the second temporary table, and deleting the first temporary table.
Specifically, the data which fails to be imported in the first temporary table is obtained, and the data which fails to be imported is copied to the second temporary table, so that only the data which fails to be imported before are imported when the next import is carried out, the data which succeeds in import before are not needed to be compared with the data of the target data table again, and the import speed is improved.
And step S270, outputting prompt information.
Specifically, the number of data successfully imported, the number of data failed to be imported, and the reason for the data import failure in the first temporary table at this time may be output.
Step S280, adjusting the data in the source data table or the target data table according to the reason of the data import failure, and re-importing the data in the source data table.
In this embodiment, for example, when the quantity of the material is imported, because the dependent data metering unit does not exist in the target data table, the import fails, and at this time, if the metering unit already exists in the source data table, the metering unit in the source data table is directly imported into the target data table; if the source data table does not have a metering unit, newly adding an input metering unit, and then importing the metering unit in the source data table into a target data table; or the metering units can be newly recorded in the target data table directly. The amount of material is then reintroduced, at which point the introduction is successful.
In one embodiment, as shown in fig. 5, step S280 includes:
step S281, copying the data in the source data table to the first temporary table;
step S282, determining whether the data in the first temporary table exists in the second temporary table, and if so, importing the data into the target data table; if the data in the first temporary table is not present in the second temporary table, no processing is performed.
In this embodiment, for example, the material data is copied to the first temporary table, at this time, data in the first temporary table is compared with data in the second temporary table, and only data in the second temporary table may be imported into the target data table as data that needs to be imported this time. For example, most data are successfully imported when the material data is imported last time, and only if the number of the materials is not successfully imported, the number of the materials is recorded in the second temporary table at this time.
As shown in fig. 6, in one embodiment, there is provided a system for data import between ledgers, including:
the data type obtaining module 310 is configured to obtain a preset data type that needs to be imported into the target account book and is selected by the user.
The data table obtaining module 320 is configured to obtain a source data table corresponding to the data category in the source account set, and obtain a target data table corresponding to the data category in the target account set.
The data importing module 330 is configured to determine whether data in a source data table conforms to a verification rule according to a preset sequence, and if so, import the data in the source data table into a target data table; and if the data in the source data table does not accord with the check rule, the import fails.
In one embodiment, the system further includes a login module, configured to obtain a name or an IP address of the source account set and a name or an IP address of the target account set, which are input by the user; acquiring login information of a source account set and login information of a target account set, which are input by a user; logging in a source account set according to the name or IP address of the source account set and the login information of the source account set; and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
In an embodiment, the data importing module 330 is further configured to determine, according to a preset sequence, whether data in the source data table needs to be imported into the target data table, if so, determine whether associated data of the data exists in the target data table, if so, determine that the associated data conforms to the check rule, and if not, determine that the associated data does not conform to the check rule; if the data in the source data table does not need to be imported into the target data table, no processing is performed.
In one embodiment, as shown in fig. 7, the data import module 330 includes:
a copying unit 331 for copying data in the source data table to the first temporary table;
a checking unit 332, configured to determine whether the data in the first temporary table conforms to a checking rule according to a preset sequence;
a temporary table importing unit 333, configured to import the data in the first temporary table into the target data table if the data in the first temporary table meets the check rule;
the processing unit 334 is configured to, if the data in the first temporary table does not meet the check rule, obtain data that fails to be imported in the first temporary table, copy the data that fails to be imported to the second temporary table, and delete the first temporary table.
In another embodiment, as shown in fig. 8, on the basis of the above system, the method further includes:
and the information prompt module 340 is configured to output prompt information, where the prompt information includes the number of data that are successfully imported in the first temporary table, the number of data that are failed to be imported, and a reason for the failure of data import.
And the re-import module 350 is configured to adjust data in the source data table or the target data table according to the reason that the data import fails, and re-import the data in the source data table.
In one embodiment, the re-import module 350 is further configured to copy the data in the source data table into the first temporary table; if the data in the first temporary table exists in the second temporary table, importing the data into a target data table; if the data in the first temporary table is not present in the second temporary table, no processing is performed.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method of data import between accounts sets, the method comprising:
acquiring a preset data category which is selected by a user and needs to be imported into a target account set; the preset data categories are multiple, and each data category corresponds to one data table in the source account set and the target account set respectively;
acquiring a source data table corresponding to the data type in a source account set, and acquiring a target data table corresponding to the data type in a target account set;
judging whether the data in the source data table accord with a check rule or not according to a preset sequence, and if so, importing the data in the source data table into a target data table; the step of judging whether the data in the source data table accord with the check rule according to the preset sequence comprises the steps of judging whether the data in the source data table needs to be imported into a target data table according to the preset sequence, if so, judging whether associated data of the data exist in the target data table, if so, judging that the associated data accord with the check rule, and if not, judging that the associated data do not accord with the check rule; if the data in the source data table does not need to be imported into the target data table, no processing is performed; the preset sequence is determined by the sequence dependency relationship among the data in the source data table, and the associated data of the data refers to the dependency data which needs to be imported into the target data table before the data is imported;
and if the data in the source data table does not accord with the check rule, the import fails.
2. The method of claim 1, wherein before the step of obtaining the preset data category selected by the user and requiring importing the target account set, the method further comprises:
acquiring the name or IP address of a source account set and the name or IP address of a target account set input by a user;
acquiring login information of a source account set and login information of a target account set, which are input by a user;
logging in the source account set according to the name or the IP address of the source account set and the login information of the source account set;
and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
3. The method according to claim 1, wherein the determining whether the data in the source data table meets the check rule according to the preset sequence is performed, and if the data in the source data table meets the check rule, the data in the source data table is imported into the target data table; if the data in the source data table does not accord with the check rule, the step of failed import comprises the following steps:
copying data in the source data table to a first temporary table;
judging whether the data in the first temporary table accord with a check rule or not according to a preset sequence;
if the first temporary table accords with the verification rule, importing the data in the first temporary table into a target data table;
and if the data in the source data table does not accord with the check rule, acquiring the data failed to be imported in the first temporary table, copying the data failed to be imported to the second temporary table, and deleting the first temporary table.
4. The method of claim 3, further comprising:
outputting prompt information, wherein the prompt information comprises the number of data which are successfully imported, the number of data which are failed to be imported and the reason of data import failure;
and adjusting the data in the source data table or the target data table according to the reason of the data import failure, and re-importing the data in the source data table.
5. The method according to claim 4, wherein the adjusting the data in the source data table or the target data table according to the reason of the data import failure, and the re-importing the data in the source data table comprises:
copying data in the source data table into a first temporary table;
if the data in the first temporary table exists in the second temporary table, importing the data into the target data table;
if the data in the first temporary table is not present in the second temporary table, no processing is performed.
6. A system for importing data between sets, the system comprising:
the data type acquisition module is used for acquiring a preset data type which is selected by a user and needs to be imported into the target account set; the preset data categories are multiple, and each data category corresponds to one data table in the source account set and the target account set respectively;
the data table acquisition module is used for acquiring a source data table corresponding to the data type from a source account set and acquiring a target data table corresponding to the data type from a target account set;
the data import module is used for judging whether the data in the source data table accord with the check rule or not according to a preset sequence, and importing the data in the source data table into the target data table if the data in the source data table accord with the check rule; if the data in the source data table does not accord with the check rule, the importing is failed;
the data import module is further used for judging whether data in the source data table needs to be imported into the target data table according to a preset sequence, if so, judging whether associated data of the data exist in the target data table, if so, judging that the associated data accord with the check rule, and if not, judging that the associated data do not accord with the check rule; if the data in the source data table does not need to be imported into the target data table, no processing is performed; the preset sequence is determined by the sequence dependency relationship among the data in the source data table, and the associated data of the data refers to the dependent data which needs to be imported into the target data table before the data is imported.
7. The system of claim 6, further comprising:
the login module is used for acquiring the name or IP address of a source account set and the name or IP address of a target account set input by a user to acquire login information of the source account set and login information of the target account set input by the user; logging in the source account set according to the name or the IP address of the source account set and the login information of the source account set; and logging in the target account set according to the name or the IP address of the target account set and the login information of the target account set.
8. The system of claim 6, wherein the data import module comprises:
the copying unit is used for copying the data in the source data table to a first temporary table;
the checking unit is used for judging whether the data in the first temporary table accord with the checking rule or not according to a preset sequence;
the temporary table importing unit is used for importing the data in the first temporary table into a target data table if the data in the first temporary table accords with a check rule;
and the processing unit is used for acquiring the data failed to be imported in the first temporary table if the data in the first temporary table does not accord with the check rule, copying the data failed to be imported to the second temporary table, and deleting the first temporary table.
9. The system of claim 8, further comprising:
the information prompt module is used for outputting prompt information, wherein the prompt information comprises the number of data which are successfully imported into the first temporary table, the number of data which are failed to be imported and the reason of data import failure;
and the re-import module is used for adjusting the data in the source data table or the target data table according to the reason of the data import failure and re-importing the data in the source data table.
10. The system of claim 9, wherein the re-import module is further configured to copy the data in the source data table into a first temporary table; if the data in the first temporary table exists in the second temporary table, importing the data into the target data table; if the data in the first temporary table is not present in the second temporary table, no processing is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410629180.XA CN105653525B (en) | 2014-11-10 | 2014-11-10 | Method and system for importing data between account sets |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410629180.XA CN105653525B (en) | 2014-11-10 | 2014-11-10 | Method and system for importing data between account sets |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105653525A CN105653525A (en) | 2016-06-08 |
| CN105653525B true CN105653525B (en) | 2020-04-10 |
Family
ID=56483374
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410629180.XA Active CN105653525B (en) | 2014-11-10 | 2014-11-10 | Method and system for importing data between account sets |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105653525B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116432604A (en) * | 2018-09-06 | 2023-07-14 | 创新先进技术有限公司 | Data verification method and device and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279542A (en) * | 2013-06-05 | 2013-09-04 | 中国电子科技集团公司第十五研究所 | Data importing processing method and data processing device |
| CN103309977A (en) * | 2013-06-14 | 2013-09-18 | 广东电网公司电力科学研究院 | Heterogeneous data resource integration method |
| CN103793424A (en) * | 2012-10-31 | 2014-05-14 | 阿里巴巴集团控股有限公司 | Database data migration method and database data migration system |
| CN103995908A (en) * | 2014-06-17 | 2014-08-20 | 山东中创软件工程股份有限公司 | Method and device for importing data |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4136994B2 (en) * | 2004-04-16 | 2008-08-20 | キヤノン株式会社 | Document processing apparatus, control method therefor, computer program, and computer-readable storage medium |
| KR101906413B1 (en) * | 2012-08-02 | 2018-10-11 | 삼성전자주식회사 | Method and apparuats for updating personal information |
-
2014
- 2014-11-10 CN CN201410629180.XA patent/CN105653525B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103793424A (en) * | 2012-10-31 | 2014-05-14 | 阿里巴巴集团控股有限公司 | Database data migration method and database data migration system |
| CN103279542A (en) * | 2013-06-05 | 2013-09-04 | 中国电子科技集团公司第十五研究所 | Data importing processing method and data processing device |
| CN103309977A (en) * | 2013-06-14 | 2013-09-18 | 广东电网公司电力科学研究院 | Heterogeneous data resource integration method |
| CN103995908A (en) * | 2014-06-17 | 2014-08-20 | 山东中创软件工程股份有限公司 | Method and device for importing data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105653525A (en) | 2016-06-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110495132B (en) | System and method for generating, uploading and executing code blocks within distributed network nodes | |
| US20180075138A1 (en) | Electronic document management using classification taxonomy | |
| JP4429356B2 (en) | Attribute extraction processing method and apparatus | |
| CN110162516B (en) | Data management method and system based on mass data processing | |
| CN108647357B (en) | Data query method and device | |
| CN103888254A (en) | Network information verification method and apparatus | |
| CN110688349B (en) | Document sorting method, device, terminal and computer readable storage medium | |
| CN106815725B (en) | Transaction verification method and device | |
| CN105337925A (en) | User account management method and apparatus | |
| CN106681854B (en) | Information verification method, device and system | |
| CN103631966A (en) | Configurable multiple-valued matching field analysis method | |
| US9355269B2 (en) | Method and system for managing uniquely identifiable bookmarklets | |
| WO2016060550A1 (en) | Electronic processing system for electronic document and electronic file | |
| CN109189849B (en) | Standardized and streamlined data entry method and system | |
| CN105653525B (en) | Method and system for importing data between account sets | |
| CN110457332B (en) | Information processing method and related equipment | |
| CN105205652B (en) | Revision method and revision system of ERP (enterprise resource planning) document | |
| JP4884364B2 (en) | Data input device, data input method, program thereof, and storage medium | |
| CN111143399B (en) | Data processing method, device, storage medium and computer equipment | |
| CN114255134A (en) | Account number disassembling method and device and storage medium | |
| US11722324B2 (en) | Secure and accountable execution of robotic process automation | |
| KR101563628B1 (en) | Error detection method, error detection apparatus and error detection system for bibliographic data of books | |
| CN103761247B (en) | A kind of processing method and processing device of error file | |
| CN112445461A (en) | Business rule generation method and device, electronic equipment and readable storage medium | |
| CN112487152A (en) | Automatic document detection method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |