On Wed, Dec 16 2015, gord chung wrote: > but when you query, you do use the original resource_id. the translation > happens on both writes and reads. while in reality, the db is will store a > different id, users shouldn't really be aware of this.
We could add another field storing the actual non-translated ID as a string I guess. > that said, because of pecan, translations don't help when our ids have '/' in > them... we should definitely fix that. Yeah, nothing is gonna help here. -- Julien Danjou /* Free Software hacker https://julien.danjou.info */
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
