Bug #8257
meta tables leaking to primary database
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
History
#2 Updated by Ovidiu Maxiniuc 3 months ago
In #8244 I discovered some meta tables are displayed as part of the primary database when the natural join relations are printed during conversion.
The testcase was:
find first _index. for each _index-field of _index, each _field of _index-field: message _field._field-name. end.and the incorrect output:
_meta._file <---- _meta._index (many-to-one on [_file-recid]) fwd._field <---- fwd._index-field (parent-id on [_field-recid])
Notice the database for _field
- _index-field
relation. When debugging, the in-memory TABLE
nodes are somehow moved from one DATABASE
parent to another. (I am guessing a side effect of processing of _User
table?)
I did not observe any immediate flaw in generated code or at runtime, but the output shows that something is not right.