Table and Query Classes good or unnecessary?
> Le 4 mars 2018 à 07:34, ADJob <firstname.lastname@example.org <mailto:email@example.com>> a écrit :
> 1. Many extra (redudant?) classes
> As you have to have at least 1 table class linked with each schema class, there will be 100+ extra classes to manage for me. If the table class were built into a schema class, it should be smarter IMHO.
> Meaning the more classes the harder to search and maintain (400 normal classes (windows, objects etc) + 100 extra table classes)
I did ask myself, long ago, why the table classes were not built into schema classes. My understanding is that it alows us to use superclasses of table classes, which I use a lot. If the data definition was linked, it would be weird.
Just my 2 cents