Proper handling of multiple connect specifications
Currently, all given connect
specifications are merged into one data structure. This makes it impossible to give meaningful error messages because information about the origin is missing once the error is detected.
Solution would be similar to the way RelAST
is handling files, i.e., have a dedicated type for one specification, and another type containing all those specifications.