Use Set instead of Seq for ColumnDef and Record / Relation access
Problem Description
Right now we're using Seq as a container for our Column's, ColumnDef's, Relation's etc. We don't need the ordering of Seq and want to avoid users/devs to use index access to columns due to the possibility of breaking those when adding columns etc.
Issue
Use Set instead of
Seq
forColumnDef
andRecord
/Relation
accessProblem Description
Right now we're using
Seq
as a container for ourColumn
's,ColumnDef
's,Relation
's etc. We don't need the ordering ofSeq
and want to avoid users/devs to use index access to columns due to the possibility of breaking those when adding columns etc.Supporting Information