Why do I get errors about UNIQUE KEYs?
On this page
SingleStoreDB does not support unique keys unless the columns in the unique key are a superset of the columns in the shard key.
This requirement is necessary because the shard key informs the query execution system which partition contains the searched value(s).
Have an application enforce the uniqueness of the proposed unique key by confirming the value to be inserted or updated does not exist in the table.
Additionally, a non-unique key can be created on the same column to increase execution time.
AUTO_argument for one column and use the
UNIQUEconstraint on the other column.
Set the shard key on the column that has the
UNIQUEconstraint on it:CREATE TABLE user_emails(id BIGINT NOT NULL AUTO_INCREMENT,email VARCHAR(140) NOT NULL,KEY(id),SHARD KEY (email),CONSTRAINT emp_email_uk UNIQUE (email));
AUTO_column's uniqueness is not enforced directly, but the way the values for it are generated guarantees uniqueness.
Create two tables for the same data set, but with different keys to enforce uniqueness on different columns.
In the following example, the
userstable enforces uniqueness and shards on the
idcolumn because a primary key acts as both a shard key and a unique index.
users_table enforces uniqueness and shards on the
A stored procedure can be used to update both tables when a new user is added, so both
UNIQUEconstraints are enforced./* Table #1 */CREATE TABLE users (id bigint NOT NULL PRIMARY KEY,email varchar(140) NOT NULL,);/* Table #2 */CREATE TABLE users_email (id bigint NOT NULLemail varchar(140) NOT NULL PRIMARY KEY,KEY(id),);
Last modified: March 14, 2023