Add `created_by` column

[ebruchez]

After discussion, out of symmetry, we'd like to add a created_by column.

So far, the username is used for that, but the meaning of that is of being an "owner", and we'd like to change the concepts. In addition, in case historical data is purged, we'd like this to be part of the current database row.

• [ ] implement change in relational persistence layer
• [ ] add way to pass creator vs. username when creating data from service PUT
• [ ] consider way to change username etc. (can be different RFE)
• [ ] automated tests for all databases
• [ ] migration doc (copy initial username to created_by)
• [ ] consider renaming created to created_time
• [ ] doc

We also discussed the idea that there could be multiple "user roles" in the future, not only "owner". That would require a new table. That is not covered by this RFE.

[ebruchez]

Q: Do we also need created_time?

[ebruchez]

• [ ] update orbeon_form_data and orbeon_form_data_attach
• [ ] update orbeon_i_current
• [ ] add $provider-2019_1-to-2023_1.sql
• [ ] add $provider-2023_1.sql

[ebruchez]

Backward compatibility considerations:

• Q: Should we allow for example 2022.1.x write to a 2023.1.x format database?
  • A: If the column is NULLable or has a DEFAULT, that should be possible. Scenario: local MySQL database that can also be accessed by 2022.1, 2021.1, etc.
• Q: How to migrate existing data?
• Q: It data was pruned on an older schema, there is no up-to-date created_by. If we update the database, then that will be populated. But if not, should we use username?

[ebruchez]

Consider: should we add a "Creator" permission, for example the current user can read/update/delete data if she is the Creator (vs. Owner)?

[ebruchez]

See also customer

[ebruchez]

Related, there could (should) be an API to change the owner.