When you add a table in Postgres, the field order is set in stone but can't be easily changed. This causes issues if new fields are added at a later date.
In terms of a layer in GeoServer; so long as it is an SQL View (or based on a view in Postgres) the fields can be re-ordered.
Notwithstanding that, the fields in an edit window are based on the actual table (as you can't edit a view). This means the field order may be less than ideal. Some scripting has been started to allow reordering of the fields on the edit forms but not completed. I've flagged it as an enhancement as it is possible to live with but may want to assign to someone at some point.
When you add a table in Postgres, the field order is set in stone but can't be easily changed. This causes issues if new fields are added at a later date.
In terms of a layer in GeoServer; so long as it is an SQL View (or based on a view in Postgres) the fields can be re-ordered.
Notwithstanding that, the fields in an edit window are based on the actual table (as you can't edit a view). This means the field order may be less than ideal. Some scripting has been started to allow reordering of the fields on the edit forms but not completed. I've flagged it as an enhancement as it is possible to live with but may want to assign to someone at some point.