Hi,
>> I don't have any particular opinion on the subject, but I found this an interesting read. Thank you for the link. I'm not a fan of uuid either, but its just a given specifics of the system I'm working with which I cannot substitute. >> I have to ask too, what benefit would a UUID type have over a string field with an index other than having to create the index? Without a uuid type I have to convert and parse/validate uuid every time I'm passing a certain object to/from the Orient db. It would be great just to be able to use uuid everywhere in the application. >> What does Cassandra return, when you ask for the value of a uid field? Cassandra returns either uuid or timeuuid: https://docs.datastax.com/en/cql/3.3/cql/cql_reference/uuid_type_r.html I'm using Go and gocql is reading it into gocql.UUID type which is [16]byte. Dennis On Wednesday, January 6, 2016 at 11:55:49 AM UTC-5, scott molinari wrote: > > I don't have any particular opinion on the subject, but I found this an > interesting read. > > https://rclayton.silvrback.com/do-you-really-need-a-uuid-guid > > I have to ask too, what benefit would a UUID type have over a string field > with an index other than having to create the index? What does Cassandra > return, when you ask for the value of a uid field? > > Scott > -- --- 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/d/optout.
