Open Stack

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 */
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151217/7b1ea22b/attachment.pgp>