Uses of Class
dev.frostlake.metastore.model.UniqueConstraint

Packages that use UniqueConstraint

Package	Description
dev.frostlake.executor.commands
dev.frostlake.metastore.model

Uses of UniqueConstraint in dev.frostlake.executor.commands

Methods in dev.frostlake.executor.commands that return types with arguments of type UniqueConstraint

Modifier and Type	Method	Description
List<UniqueConstraint>	ColumnDefinitionParser.parseUniqueConstraints(FrostlakeParser.ColumnListContext ctx)	The table-level UNIQUE constraints of a column list — ONE per declaration, so UNIQUE (a, b) is a single multi-column constraint rather than one constraint per column.

Uses of UniqueConstraint in dev.frostlake.metastore.model

Methods in dev.frostlake.metastore.model that return types with arguments of type UniqueConstraint

Modifier and Type	Method	Description
List<UniqueConstraint>	Table.getDeclaredUniqueConstraints()	Only the UNIQUE constraints declared at TABLE level, as stored — for persistence and structural copies, which must not turn a column-level UNIQUE into a table-level constraint on reload.
List<UniqueConstraint>	Table.getUniqueConstraints()	Every UNIQUE constraint on this table, ONE entry per constraint (never one per column): the table-level constraints as declared — a UNIQUE (a, b) is a single constraint with a single name — followed by a single-column constraint for every unique column none of them spans, which is what a bare column-level UNIQUE declares.

Methods in dev.frostlake.metastore.model with parameters of type UniqueConstraint

Modifier and Type	Method	Description
void	Table.addUniqueConstraint(UniqueConstraint constraint)	Add an already-built UNIQUE constraint — the CREATE TABLE parse path and snapshot restore.