Commit e424eaa
fix: resolve association/attribute and entity/enumeration ambiguity (#50)
Bug 1: CREATE/CHANGE OBJECT wrote associations into the Attribute field
because the dot-contains heuristic failed for unqualified names like
Child_Parent. New resolveMemberChange() queries the domain model to
determine if a member is an association or attribute. Handles both
bare names (Order_Customer) and already-qualified names
(MfTest.Order_Customer) without double-qualifying.
Bug 2: DECLARE with entity types produced DataTypes$EnumerationType
instead of DataTypes$ObjectType because the visitor cannot distinguish
entities from enumerations. The executor now resolves this ambiguity
by checking the domain model via isEntity().
Both fixes fall back gracefully when no reader is available.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>1 parent 4fda6ed commit e424eaa
1 file changed
+23
-6
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
745 | 745 | | |
746 | 746 | | |
747 | 747 | | |
| 748 | + | |
| 749 | + | |
748 | 750 | | |
749 | 751 | | |
750 | 752 | | |
| |||
758 | 760 | | |
759 | 761 | | |
760 | 762 | | |
| 763 | + | |
| 764 | + | |
| 765 | + | |
| 766 | + | |
| 767 | + | |
| 768 | + | |
| 769 | + | |
| 770 | + | |
| 771 | + | |
| 772 | + | |
| 773 | + | |
761 | 774 | | |
762 | 775 | | |
763 | 776 | | |
764 | 777 | | |
765 | 778 | | |
766 | | - | |
767 | | - | |
| 779 | + | |
| 780 | + | |
768 | 781 | | |
769 | 782 | | |
770 | 783 | | |
771 | | - | |
772 | 784 | | |
773 | | - | |
774 | | - | |
| 785 | + | |
| 786 | + | |
775 | 787 | | |
776 | 788 | | |
777 | 789 | | |
778 | 790 | | |
779 | | - | |
| 791 | + | |
| 792 | + | |
| 793 | + | |
| 794 | + | |
| 795 | + | |
| 796 | + | |
780 | 797 | | |
781 | 798 | | |
782 | 799 | | |
| |||
0 commit comments