Russian characters in primary key exceeding 500 characters

[David Hardwick]

And how are you?

We have an Google Apps Administration product in the Google Apps Marketplace where we use the fullpath of an Organizational Unit as our datastore's primary key.

When we get the path for an Organizational Unit in Russian, for example, the characters are then converted to escaped ASCII by the datastore (or by objectifiy?) ...I presume because this is a requirement for the primary key in the datastore to be in this format or because we aren't smart enough to figure out how to do it otherwise -- the latter possibility is very viable!   

Due to the conversion, we then exceed the 500 character limit for the primary key for Russian companies that have  Organizational Units that are three or four levels deep.

Is there anyway to store non-ASCII characters natively in the datastore's primary key or a more compact way to do this other than the current method that the datastore (or by objectify?) is doing by default? 

Yes, we could come up with some other opaque key, but for better or worse, this concept of the Org Unit Path as our primary key is where we are at and we have 1000s of domains where this is just fine, so it's an edge case at this point that we would like to try to find a solution that would work with our current design.

Rock on,

  David Hardwick

--

We make Google Apps even better.

David Hardwick
CTO
david.h...@bettercloud.com
 
Signature by Flashpanel

See us in PandoDaily: BetterCloud Debuts FlashPanel to Help Google Beat Microsoft