to include surrounding words. The fragment-based mode is thus more useful when the query matches span large sections of the document, or when it’s desirable to display multiple matches. In either mode table constraint is the same as that of a unique column constraint, with the additional capability to span multiple columns. The constraint therefore enforces that any two rows must differ in at least one choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span VMware Greenplum 7 Documentation VMware by Broadcom 1555 Name Alias Size Range Description json

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span VMware Greenplum v6.18 Documentation VMware, Inc. 1471 json 1 byte + json size json of any

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span VMware Greenplum v6.19 Documentation VMware, Inc. 1480 json 1 byte + json size json of any

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span VMware Greenplum v6.17 Documentation VMware, Inc. 1407 json 1 byte + json size json of any

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary

unique table constraint is the same as that for column constraints, with the additional capability to span multiple columns. For the purpose of a unique constraint, null values are not considered equal. The choice for integer interval [ fields ] [ (p) ] 16 bytes -178000000 years to 178000000 years time span json 1 byte + json size json of any length variable unlimited length jsonb 1 byte + binary