Good idea Daniel Wang [X],
On my side I would like to have no default values for dirTable and dirColName in cfg files. This fields imply that the table is a "child" table, so having default value for them can be ambiguous.
Furthermore it seems that Object/ObjectId names, which are current default in loader, won't be used in most of our future cases.
Maybe also we should have a nice and easy to remmeber/understand vocabulary for director/child, (like for example parent/child, maestro/musician, guide/follower, leader/follower, mentor/pupil, or principal/subordinate, ...). Indeed, in my understanding of english child and director aren't related, isn't it?
One other point, it seems that part.id and dirColName both relate to FK of director table. If yes, maybe we should unify these two fields in cfg files?
Thanks,
Fabrice
Good idea Daniel Wang [X],
On my side I would like to have no default values for dirTable and dirColName in cfg files. This fields imply that the table is a "child" table, so having default value for them can be ambiguous.
Furthermore it seems that Object/ObjectId names, which are current default in loader, won't be used in most of our future cases.
Maybe also we should have a nice and easy to remmeber/understand vocabulary for director/child, (like for example parent/child, maestro/musician, guide/follower, leader/follower, mentor/pupil, or principal/subordinate, ...). Indeed, in my understanding of english child and director aren't related, isn't it?
One other point, it seems that part.id and dirColName both relate to FK of director table. If yes, maybe we should unify these two fields in cfg files?
Thanks,
Fabrice