主键应该是唯一的常量

电子邮件地址随着季节的变化而变化。作为查找的辅助键很有用，但作为主键不太合适。

我还要指出，电子邮件是一个糟糕的选择，使一个独特的领域，有些人，甚至是小企业共享一个电子邮件地址。和电话号码一样，电子邮件也可以重复使用。Jsmith@somecompany.com很容易属于一年前的约翰·史密斯，两年后的茱莉亚·史密斯。

电子邮件的另一个问题是它们经常变化。如果你用这个键连接到其他表，那么你也必须更新其他表，当整个客户公司更改他们的电子邮件时，这可能会对性能造成相当大的影响(我曾经见过这种情况)。

使用GUID作为主键…这样，当你执行INSERT操作时，你就可以从程序中生成它，而不需要从服务器获取响应来找出主键是什么。它在所有表和数据库中都是唯一的，如果有一天你截断了表，自动增量被重置为1，你不必担心会发生什么。

字符串比较比int比较慢。但是，如果您只是使用电子邮件地址从数据库检索用户，那么这并不重要。如果您有多个连接的复杂查询，那么这很重要。

如果在多个表中存储有关用户的信息，则用户表的外键将是电子邮件地址。这意味着您将多次存储电子邮件地址。

使用电子邮件地址作为主键的缺点:

Slower when doing joins. Any other record with a posted foreign key now has a larger value, taking up more disk space. (Given the cost of disk space today, this is probably a trivial issue, except to the extent that the record now takes longer to read. See #1.) An email address could change, which forces all records using this as a foreign key to be updated. As email address don't change all that often, the performance problem is probably minor. The bigger problem is that you have to make sure to provide for it. If you have to write the code, this is more work and introduces the possibility of bugs. If your database engine supports "on update cascade", it's a minor issue.

使用电邮地址作主键的优点:

You may be able to completely eliminate some joins. If all you need from the "master record" is the email address, then with an abstract integer key you would have to do a join to retrieve it. If the key is the email address, then you already have it and the join is unnecessary. Whether this helps you any depends on how often this situation comes up. When you are doing ad hoc queries, it's easy for a human being to see what master record is being referenced. This can be a big help when trying to track down data problems. You almost certainly will need an index on the email address anyway, so making it the primary key eliminates one index, thus improving the performance of inserts as they now have only one index to update instead of two.

在我看来，这两种情况都不是十拿九稳的。当有实用的键时，我倾向于使用自然键，因为它们更容易使用，而且在大多数情况下，缺点并不太重要。

是的，如果您使用整数来代替会更好。您还可以将电子邮件列设置为唯一约束。

是这样的:

CREATE TABLE myTable(
    id integer primary key,
    email text UNIQUE
);