dj.getSchema does not correctly recognize python-generated Part tables
Opened this issue · 2 comments
If creating a Master>Part relation via Part tables in python, the corresponding tables as read out by dj.getSchema() instead categorizes them as manual, and renames them by concatenating the table names (i.e. creating a MasterPart table).
This means that when adding them manually to .m files within the +package folder using dj.new will also incorrectly populate the comment header in these files.
Related to this, the method for adding these tables to .m files within a +package folder by typing MasterPart into the dj.new prompt does not appear to be documented anywhere directly, unless I missed it.
edited for clarity
It seems this also causes other problems with relational algebra.
Calling package.Master() & package.Part() for instance does not link the tables on the primary key. Editing the master property in the package\Part.m file does not fix this.