Hi, You can use BYTE type as UUID store so it can only consume 16 bytes as I remember. And bytes can be indexed.
Is this solution OK for you ? On Thu, Jan 30, 2014 at 7:58 PM, <[email protected]> wrote: > Hi, > > I'm using OrientDB to persist Events into an extended activity log (the > activity stream) and these events are identified by deterministic IDs > (version 3 UUID). > That means that their ID can even be calculated on the client before they > are persisted. > > - A unique signature is processed with: java.util.UUID > nameUUIDFromBytes(<signature>) > > A typical ID looks like this 172ecd63-9c62-380d-a0a1-c45ca8883bc7 (more > information here <http://en.wikipedia.org/wiki/UUID#Definition>) and > currently I'm forced to store it as a String. > > Either of two things would make my life considerably easier: > > - Support for efficient storage of UUIDs in OrientDB making UUIDs > first class citizens > - Support for transient properties that are only indexed but not stored > > I know I can implement the latter with an index that I maintain myself but > I will only do that as a last resort. > > Any comments? :) > > Very best regards, > -Stefán > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
