You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I am using cottontail for my master thesis. Thank you for your work!
It seems to me that the primary flag in the column definition of an entity has no effect.
It is possible to insert multiple entries with the same string ID into an entity with primary key set for the column.
Furthermore, the CLI command "entity about schema entity" does not list primary information for the columns.
Best,
Simon
The text was updated successfully, but these errors were encountered:
Since as of version 0.15.0 of Cottontail DB, a column can already be decleared as primary key, I would suggest the following additions to finalise this feature request:
Marking a column as primary-key force-creates an index for that column, which cannot be dropped. Furthermore, primary-key columns cannot be null.
Upon INSERT, unique constraint of a value must be enforced using said index (which should already be the case, but needs to be handled properly).
Hello! I am using cottontail for my master thesis. Thank you for your work!
It seems to me that the primary flag in the column definition of an entity has no effect.
It is possible to insert multiple entries with the same string ID into an entity with primary key set for the column.
Furthermore, the CLI command "entity about schema entity" does not list primary information for the columns.
Best,
Simon
The text was updated successfully, but these errors were encountered: