Migration from editor to user and vice-versa
| Version | Change |
|---|---|
| v1.0 | Initial version |
| v1.1 | Remove trigger |
<v1.1>
Exporting of editor and importing in user will be done manually.
We need a cron for user to move any changes to the editor in the hub database. All records from user must be present in editor with the same id and names. Other field values will also be updated, but these are the ones that carry any value for the system.
We will need to handle all eligible records in hub_alpha>client. We are to exclude the clients with variations of localhost, with names default, containing the value callbacks or api and with suffix _mysqli . These are system connections that are for internal purposes. This cron is to keep it working but we cannot make it a trigger for now. This will be obsolete once we stop using the “Alpha” project.
</v1.1>
@Product it is good if we unify all user ids from all projects so that we do not have differences in ids.