The phrase "as primary keys" is correct and usable in written English.
It can be used in the context of databases or data management when referring to unique identifiers for records in a table.
Example: "In our database design, we will use the customer ID and order ID as primary keys to ensure each record is unique."
Alternatives: "as unique identifiers" or "as key identifiers".
The attributes of the foreign key list are not necessarily considered as primary keys.
One common vendor extension is using some method of generating a sequence of integers to use as primary keys.
Output identifier types were the subset of input types that act as primary keys in public databases, i.e., ChEBI ID, HMDB ID, KEGG CID and PubChem CID.
This can be achieved by constructing the sales table such that records contain foreign keys for the user and product tables (implying that these contain attributes classified as primary keys).
These identifiers were introduced for several reasons: the sequential integers used as primary keys are valid only for a single database version and hence not stable.
The ORF identification tags (ORF ID) assigned to proteins of fungal pathogens as given in the respected database repositories mentioned earlier were used as primary keys.
Object relationships in UML models are implemented as primary key and foreign key in database.
The City, Department, Doctor and Hospital tables have an "Id, Name" structure, with "Id" as primary key.
The event is stored and these attributes are passed as primary key attributes: day as partition key, month and year as clustering keys and (gh_numeric) as either part of clustering keys or a secondary indexed column value.
Table 3 is shown having R_id as primary key in all related tables along with other attributes and CKP_F being a flag field to denote the modification of records.
This criteria is achieved through sorting by the scores as primary key and the end positions as secondary keys of all alignments followed by the overlap comparisons among the sorted candidates.
