Go 101 (Golang 101) v1.21.0Embedding - type extension in the Go way. §25. Type-Unsafe Pointers §26. Generics - use and read composite types §27. Reflections - the reflect standard package. Some Special Topics §28. Line Break for more information about above built-in basic types and their value literals. Some other types (composite types) will be introduced later in other articles. Line 22 is an assignment. Line 5 declares a kinds of code elements in Go programs. chan, interface, map and struct are used as parts in some composite type denotations. break, case, continue, default, else, fallthrough, for, goto, if, range, return0 码力 | 610 页 | 945.17 KB | 1 年前3
Go 101 (Golang 101) v1.21.0Embedding - type extension in the Go way. §25. Type-Unsafe Pointers §26. Generics - use and read composite types §27. Reflections - the reflect standard package. Some Special Topics §28. Line Break Rules more information about above built- in basic types and their value literals. Some other types (composite types) will be introduced later in other articles. Line 22 is an assignment. Line 5 declares a kinds of code elements in Go programs. chan, interface, map and struct are used as parts in some composite type denotations. break, case, continue, default, else, fallthrough, for, goto, if, range, return0 码力 | 880 页 | 833.34 KB | 1 年前3
peewee Documentation Release 2.10.2model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. verbose_name = None – string representing the “user-friendly” name of this field help_text either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 275 页 | 276.96 KB | 1 年前3
peewee Documentation
Release 3.5.0model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying an index on this column unique = False – create a unique index on this column. See also adding composite indexes. column_name = None – explicitly specify the column name in the database. default = None either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 347 页 | 380.80 KB | 1 年前3
peewee Documentation Release 3.4.0model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 349 页 | 382.34 KB | 1 年前3
peewee Documentation Release 3.0.0model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 319 页 | 361.50 KB | 1 年前3
peewee Documentation Release 3.6.0model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying an index on this column unique = False – create a unique index on this column. See also adding composite indexes. column_name = None – explicitly specify the column name in the database. default = None either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 377 页 | 399.12 KB | 1 年前3
peewee Documentation Release 3.1.0model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key0 码力 | 332 页 | 370.77 KB | 1 年前3
CakePHP Cookbook Documentation 5.xNOW(), NOW()); You may have noticed that the articles_tags table uses a composite primary key. CakePHP supports composite primary keys almost everywhere, allowing you to have simpler schemas that don’t created modified Note Some adjustments to the generated code might be necessary. For example, the composite primary key on articles_tags will be set to auto-increment both columns: $table->addColumn('article_id' NOW(), NOW()); You may have noticed that the articles_tags table uses a composite primary key. CakePHP supports composite primary keys almost everywhere, allowing you to have simpler schemas that don’t0 码力 | 1080 页 | 939.39 KB | 1 年前3
Hyperledger Fabric 1.4.8 Documentationfeatures of a Fabric ledger: Query and update ledger using key-based lookups, range queries, and composite key queries Read-only queries using a rich query language (if using CouchDB as state database) Read-only best implemented as a set of individual Fabric states, whose composite key associates the state with its list. In this way, each state’s composite key is both unique and supports effective list query. Representing Fabric states Notice how each paper in the list is represented by a vector state, with a unique composite key formed by the concatenation of org.papernet.paper, Issuer and Paper properties. This structure0 码力 | 699 页 | 9.02 MB | 1 年前3
共 137 条
- 1
- 2
- 3
- 4
- 5
- 6
- 14













