Dear MonetDB developers, from my own experiences regarding database engine design, I know that SQL constraints can be used to increase performance because the query planner can use them to reason about certain regularities in the data. On the other hand, they come with a cost as the engine is supposed to enforce them. Are there any common rules on how constraints and performance correlate in MonetDB, which could be used to adapt a schema to work especially fast with MonetDB? Best regards, Isidor