Detect multiple auto increment or primary key columns on table creation #8
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently the implementation only checks for duplicate primary keys (or auto increments) during table alteration in
Database::enforceSchema(). The implementation should also prevent this situation during table creation.