postgresql.txt（postgresql.txt）.docVIP

postgresql.txt（postgresql.txt） Table definition: For any relational database, tables are the core and most basic object units of data storage. Now lets start from here. 1. create table: CREATE, TABLE, products Product_no integer, Name text, Price numeric ); 2. delete tables: DROP TABLE products; 3. create tables with default values: CREATE, TABLE, products Product_no integer, Name text, The price numeric DEFAULT 9.99 --DEFAULT is the keyword, and the subsequent value 9.99 is the default value of the field price. ); CREATE, TABLE, products The product_no SERIAL, --SERIAL type field indicates that the field is a self - increasing field, and is exactly equivalent to the Sequence in Oracle. Name text, Price numeric DEFAULT 9.99 ); Output as: NOTICE:, CREATE, TABLE, will, create, implicit, sequence, products_product_no_seq, for, serial, column, products.product_no 4. constraint: Checking constraints is the most common constraint type in a table, which allows you to declare that a value in a field must satisfy a Boolean expression. Not only that, we can also declare table level check constraints. CREATE, TABLE, products Product_no integer, Name text, The value of the --price field must be greater than 0, otherwise inserting or modifying the value of the field will cause an error in violation. It should also be noted that the check constraint -- anonymous constraints, that is, when the table definition is not shown, name the constraint, so that the PostgreSQL will be based on the current table name, field name, and constraint type, - automatic naming for this constraint, such as: products_price_check. Price, numeric, CHECK (price 0) ); CREATE, TABLE, products Product_no integer, Name text, -- the check constraint for this field is displayed, named positive_price. The advantage of this approach is that it can be operated directly according to the name when the constraint is maintained in the future. Price, numeric, CONSTRAINT, positive_price, CHECK (price 0) ); The follow