HF RL Explorer

Constructor auto-mapping should use argument names, not column order, and avoid double-mapping of fields

Constructor auto-mapping should use argument names, not column order, and avoid double-mapping of fields: a task in LegoFlow-SWE (Harbor dataset). MyBatis’s constructor auto-mapping (used when autoMappingBehavior is PARTIAL or FULL ) matches constructor arguments to result set columns by column…

The task

MyBatis’s constructor auto-mapping (used when `autoMappingBehavior` is `PARTIAL` or `FULL`) matches constructor arguments to result set columns **by column position (order)**, not by name. This leads to incorrect field assignments whenever the SQL column order differs from the constructor parameter order. For example:

Part of Lego-X/LegoFlow-SWE.