@elizarov I ran into this in the case of jOOQ. It generates "record" classes that take in many named parameters. Their order depends on the order of the source database table columns.
Mind you, jOOQ now actually supports generating Kotlin record classes but it makes all fields nullable (even those that are not null in database) which makes them hard to work with compared to the Java version.