You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the generated tables structure, it looks like the fields are added in alphabetical order, not the order they are declared in the type definitions. That means that, for example, the primary auto-increment id key can be somewhere in the middle instead of first, it looks quite messy this way when looking at the data in phpMyAdmin for example.
Is that a limitation of how macros work, or would it be possible to maintain the original declaration order from the data type definitions?
The text was updated successfully, but these errors were encountered:
IIRC haxe orders fields of anonymous types alphabetically (I assume this makes unification between structures faster). I guess we could try to restore order via field position though.
I don't remember this happening before, so I'm guessing newer haxe versions supply fields in a different order. We rely on field order here too: #47 (comment)
Looking at the generated tables structure, it looks like the fields are added in alphabetical order, not the order they are declared in the type definitions. That means that, for example, the primary auto-increment id key can be somewhere in the middle instead of first, it looks quite messy this way when looking at the data in phpMyAdmin for example.
Is that a limitation of how macros work, or would it be possible to maintain the original declaration order from the data type definitions?
The text was updated successfully, but these errors were encountered: