feat(flex): Ensure Deterministic Column Ordering in jansPerson / gluuPerson Schema Across Installations

[mzico]

Summary

Column ordering in the jansPerson (formerly gluuPerson) table is inconsistent across Flex + PostgreSQL installations. For example, the "profile" attribute may appear as column 4 in one environment and column 24 in another. Although queries are by name, one of our enterprise customers relies on fixed column positions for downstream ingestion pipelines.

Problem

Schema generation does not enforce a consistent column order.

Result: each installation may produce different ordinal positions.

This causes issues for customers using strict schema validation (Kafka, ETL, etc.).

Expected Behaviour

New installations should always generate the jansPerson table with the same, deterministic column ordering, regardless of environment.

[moabu]

I think this is a valid issue and we must address it. @mzico this issue should be moved to https://jans.io

[devrimyatar]

I explored setup. Attribute names (in rdbm they are column names) are stored in a list. So they should be in the same order for all installations. I explored three installation (one mysql and two psql), all attributes are exactly in the same order. See attached files.

jans-ubuntu22-mysql.txt
jans-suse15-psql.txt
jans-ubuntu22-psql.txt