Following on from #22 I'm curious about why unique properties are unsupported? Presumably you could generate UUIDs for String properties and for numeric properties you could have a singleton instance of AtomicInteger and call getAndIncrement() on that every time a new value is required (performing a widening conversion to a float, double, etc. if required).
Of course if there are more values required for an integer property than there are available in the range Integer.MIN_VALUE..Integer.MAX_VALUE then you're stuffed, but this is a pretty unlikely case.
I guess I must be missing something, but what is it? If this sounds like a viable solution, I might give it a go myself.
Following on from #22 I'm curious about why unique properties are unsupported? Presumably you could generate UUIDs for String properties and for numeric properties you could have a singleton instance of
AtomicIntegerand callgetAndIncrement()on that every time a new value is required (performing a widening conversion to a float, double, etc. if required).Of course if there are more values required for an integer property than there are available in the range
Integer.MIN_VALUE..Integer.MAX_VALUEthen you're stuffed, but this is a pretty unlikely case.I guess I must be missing something, but what is it? If this sounds like a viable solution, I might give it a go myself.