Aurelius entity property creation order

Table column order with Data Modeller does not match with the generated Aurelius entity model and so with the database. Is there some configuration to force them match?


That's by design, note that it keeps the order, but it adds the primitive-typed fields first, and then the association fields. Even though JOB_STATUS_ID is a "regular" database field, in Aurelius it's mapped as an association, thus the reason why it's listed after the "non-association" properties.