We use TDynamicProperties to allow our customers to define and use custom fields.
As a next step, we want to offer our customers custom tables, i.e. completely freely definable tables.
The databases are currently managed exclusively via the TDatabaseManager.
These tables should, above all, be easy to use via XData,
and also be manageable internally through generic forms.
Is there a simple approach that I might currently be missing that would allow us, using Aurelius, to define and manage multiple tables with a single class—without having to define empty placeholder classes such as
TCustomTable001
TCustomTable002
and so on?
Are there any hints you can give me regarding what I should already take into account today when designing my classes for this?
My current approach would be to create a base class that handles the fundamental logic and to provide customers with n placeholder classes.
Once the feature becomes available, everything would then fall back to the base class and the generated placeholders would be removed.
The idea is that this would not be tied to a real class. Everything will be dynamic, so no classes or dynamic properties, you would simply have an object with property names and values you can access. Well, you can think it this way: Aurelius will provide you already with a base class that has dynamic properties in it.