SN/T 4741-2016 in English

Technical Background of the Standard

This standard, as a foundational specification for the informatization of the inspection and quarantine industry, was developed based on the GB/T 1.1-2009 standardization guidelines. It focuses on addressing the issue of uniform database naming in the development of inspection and quarantine information systems. The standard was first published in December 2016 and officially implemented in July 2017.

Core content analysis

3.1 Database object naming system

3.5 Primary Key Naming Standards

Primary key fields must use the prefix PK_, in the format: PK_table name_field name. For example, the primary key of the declaration record table should be named: PK_SPV_INSPECT_RECORD

3.6 Special Conventions for Foreign Keys

Foreign key fields use the structure of the prefix FK_ followed by the associated table name and the associated field name, such as: FK_DECL_CERT_DECLNO. The standard specifically emphasizes that foreign keys must include a complete reference relationship description.

Implementation Recommendations

4.1 Data Type Identification Specifications

Article 4.2.23 of the standard specifies the data type prefix rules in detail, for example:

• vc_ indicates the VARCHAR2 type
• n_ indicates the NUMBER type
• d_ indicates the DATE type

4.2 Enterprise Application Recommendations

It is recommended that development teams establish a naming standard checking tool and integrate automated verification into the CI/CD process. For the transformation of historical systems, please refer to the transition plan provided in the standard appendix.