Order of fields in table defination, does it matter?

pete letkeman

In MySQL the order of the fields in the table defination matter, to a degree, performance wise.
For instance for quicker results you want to have your primary and foreign keys defined first and if they can be integer even better. Then you want:
1. booleans
2. enums
3. tinyint
4. int
5. long
6. date/time
7. character
8. varchar
9. blob

The reasoning is that keys are read first and almost always have values.
Next we go by amount of memory the data type utilizes and the fields which are more likely to have a value then those that don't.

I think that Xano uses Postgres under the hood and the table editor does allow you to change the ordering of the fields.
Does the ordering of the fields make any performance changes in Xano/Postgres?

Michael Udinski

Hey  the order of your fields should not matter in Xano