Hi all Any update on this feature? Is it available?
Thanks, Noorul On Friday, December 21, 2012 8:16:15 PM UTC+3, Krisztian Kocsis wrote: > > Hi Luca! > > It seems good at least for me! > > On Friday, December 21, 2012 12:49:27 PM UTC+1, Lvc@ wrote: >> >> Hi, >> we've this issue: https://github.com/nuvolabase/orientdb/issues/367 >> >> I changed its milestone to assign it to 1.4.0. I'd like to use this >> thread to share some implementation details. How to implement it? We've so >> many options, this is just one: >> >> 1. add the support for sequence in Metadata, like >> db.getMetadata().getSequenceManager() -> OSequenceManager >> 2. OSequenceManager could have getSequence(name), dropSequence(name) >> that manages OSequence objects >> 3. OSequence wil have: >> 1. a long number that keeps the value >> 2. next() : long, >> 3. current() : long, >> 4. reset() >> 4. We could create an ad-hoc cluster "osequence" to save all the >> instances there >> 5. OSequenceManager could cache the value to stay in memory and flush >> to disk at every next(), but the strategy could change per-sequence >> 6. For remote protocol this should be managed at server-side only >> like indexes, so 2 clients that call next() do a rpc to the server >> 7. In next release we could pre-assign a block of numbers to each >> client to minimize network calls >> >> WDYT? >> >> Lvc@ >> >> >> >> On 20 December 2012 23:25, Maximos Sapranidis <[email protected]> >> wrote: >> >>> +1 >>> >>> -- >>> >>> >>> >>> >> >> -- --- 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.
