Relations Module

@x1250 The Schemas dependency is essential to the design of the module, otherwise it wouldn’t know which tables are related to others and they nature of their relationship. If you don’t like the database-scanning nature of Schemas you can still define you schema in a single flat file using the DirectoryHandler. If you have other concerns about Schemas I’m open to hearing them.

@BasicApp the constructor isn’t essential but the code it runs needs to happen - I could move it to an init() function of some sort but then either you would be responsible for initializing or it would have to be checked on every method call. I’m open to input.

Hello MGatner. Right, my point is that an add-in like this shouldn't depend on the schema guesswork, since that limits its application. The guess work should be minimal and the schema stuff optional.

Also, in real applications, sometimes there is no way any programmed guess work will be able to determine any relations between tables.

IMO, relations should be defined directly in the model and nowhere else and the schema thing should be optional.

I hope someone can do it, because it is out of my technical capacity for now