Queries about the transaction (pay special attention to distinguish between the original transaction code and the code of this query):
1. query the transaction is successful, the success of the original transaction
2. Query the transaction is successful, the original transaction fails
3. Query the transaction is successful, the original transaction processing
4. Query the transaction fails, no treatment, waiting for the next query (query the transaction fails, be careful not to turn failure, the query transaction failure may be caused by network problems)
The next day the problem (on the original transaction to send a certain period of time if the original transaction occurred. If the query Feb. transaction occurred on the 2nd, February 3's visit to queries should be sent to the original transaction date is February 2, 2009, If you send 2 Yue 3 the date the Bank could lead to the return of the original transaction does not exist)
6. The original transaction does not exist can not rashly set to fail, has failed no such transaction set capital loss risk.
The original transaction does not exist may be caused by the following situations:
1) due to network reasons, first to query the transaction, after the original transaction that led to the investigation no such transaction;
2) the original transaction sent to the other party, the other party has failed the check, the transaction is not for falling, to go back when the query returns no such transaction;
3) when the transaction or query reach the other side, the original transaction has reached the other side but the other side is still processing, not for falling, this time will be no such check transaction)
About Query tab properties (test / production line the amount of difference data):
1. Query the real-time requirements. Real-time performance is not high even general library equipment, consider the synchronization mechanism of the main library library equipment, library equipment may delay or even longer delays in half an hour.
2. Frequency query. If the query higher frequency, usually even by the library. If even the main library, if encountered high-frequency access, the whole main library hung up, prone to appear on the main trading link problem, very dangerous.
3. The amount of data queries. Paging function + limitations, the amount of control data. If a large amount of data query, must have a paging function. And whether to add more restrictions or time limits to prevent excessive data returned by a query, into the application memory the application to hang out. If this query and export capabilities, this export function also have to pay attention.
4. If there is a report the amount of data export functions, pay attention to export. When testing, it can test a large number of 10W, 50W, a large number of 100w and other export reference data volume production lines.