If we do not do it now, then doing it later will be a real pain because the db content would have to be deduplicated for a proper migration.
However, giving more thinking to that, I'm not even sure we should do this de-duplication.
The reason is that with the deduplication, when an API user reads an object that had been created earlier, what he will get for the route_target fields will be different from what he will have specified initially.
I am not sure that the possible confusion coming from this is worth the very minor optimisation in the DB fields.
If we do not do it now, then doing it later will be a real pain because the db content would have to be deduplicated for a proper migration.
However, giving more thinking to that, I'm not even sure we should do this de-duplication.
The reason is that with the deduplication, when an API user reads an object that had been created earlier, what he will get for the route_target fields will be different from what he will have specified initially.
I am not sure that the possible confusion coming from this is worth the very minor optimisation in the DB fields.