We strongly suggest using AutoKey for your Primary Keys. We do NOT suggest that you embed any meaning in the key itself (say an "order number" with the date as part of it) as these keys are difficult to generate and maintain.
The most common exception to the "always use an AutoKey" rule of thumb is look-up tables. For example, you might have a list of U.S. states where a two character column containing the state abbreviation is the logical Primary Key for the table.
We suggest that you NEVER use Composite Primary Keys (these are Primary Keys composed of multiple columns). If you are an advanced database designer, we suggest you instead use an AutoKey for the Primary Key and then add an additional UNIQUE INDEX over the columns that are required to be unique. You can do so easily via Tools > SQL Console... with a command like the following: