>Yes! The primary key will only be made up of 12 bytes. By using an
>integer you ensure that your entire column is in the key.
I've faced one problem with integer foreign key. I want to sort the results
of a query by two fields, one of them is the foreign key. If I use integer
foreign key and if I want to order the results by it, the order of key
values (integers) must coincide with the order of string values. And if I
have to insert some items into the table? In this case I'll have to update
the primary key and of course all foreign keys that reference my table.
There wouldn't be such problem if I use string primary/foreign key (for
example, if I use a string title as a primary key, not some integer
(sorting the query results by two fields from different tables is slow)