A method for storing and analyzing ordinary invoice data

Abstract

The present invention is a method for storing and analyzing ordinary invoice data, using database form one record + invoice quick inspection + microstructure + JAVA reflection class secondary analysis; automatically identifying the main pole and detailed main information through the base class of the invoice template; The template code parsed in the template base class automatically goes to the template management class to find the corresponding specific invoice template class; then the specific invoice template class is generated through reflection technology, and the nodes in the microstructure are fully analyzed; finally, the specific invoice template class is returned The invoice template class. The invention can ensure the integrity and consistency of the invoice data, can directly perform quick query without secondary analysis, and automatically performs secondary analysis on the microstructure, and can be easily packaged to simplify the access of invoices.

Description

technical field [0001] The invention relates to a technology for storing and analyzing invoice information in a network invoice issuing system, in particular to a method for storing and analyzing common invoice data. Background technique [0002] At present, the storage and analysis methods for ordinary invoices with many samples are purely based on the database, and at most they are stored in conjunction with the code table. When storing, there are usually the following two methods: one main table plus multiple sub-tables or one Each template invoice corresponds to a table. [0003] For the way of adding multiple sub-tables to one main table, it is to store the invoices in common in one main table, and store the invoice details of different templates in different sub-tables according to the template type, and check the main table first when querying. Then look up the subtable according to the template type, so that a complete invoice can be parsed out. For a template invo...

AI Technical Summary

Problems solved by technology

[0004] The problems existing in the above existing technologies are: ⑴The method of adding multiple sub-tables to one main table: a) The main key of the sub-table is a mandatory external key of the main table to maintain consistency, which puts a great pressure on the performance of the database; b) Since there are multiple rows in the subtable, it is very easy to delete one row, which is not conducive to maintaining integrity; c) Since there are many tables and maintenance is difficult, when backing up invoice data, multiple table backups are required, and deadlocks are easily formed, and It is not conducive to the use of partition table technology in large relational databases to achieve partition management

⑵A method in which a template invoice corresponds to a table: a) Due to the need to save multiple backups for the common parts, the data redundancy is relatively large; b) Since there are multiple rows in the sub-table, it is very easy to delete one, thus It is not conducive to maintaining integrity; c) Since there are many tables and it is difficult to maintain, when backing up invoice data, multiple table backups are required; d) It is necessary to determine which data table to access through software. If a user has multiple tickets, give the application provides difficulties

Images