A quick update for this request:
We’re substantially there, but we still need to make the experience better. We’re still working on this.
Moving this back to under review.
Will you please give us more information on your use case for this request?
What i'm trying to do is exactly what Jay Traband is saying is his answer to the stackoverflow question.
I'll reproduce the answer here:
Actually having a multipart key where part of the key is autogenerated is actually pretty common. This usually occurs with legacy databases where the primary key consists of a foreign key property and a 'autogenerated' sequence number property. Usually this autogenerated key is not globally unique by itself, but only in conjunction with the foreign key property. Think of an orderDetail with a foreign key of "OrderId, SequenceNumber".
What doesn't seem to make as much sense is when the primary key consists of more than one autogenerated property.
In Breeze the autogenerated keys are intended to be globally unique. Whereas, in the multipart key mentioned above the SequenceNumber would not be globally unique ( and if it were then why not make it the primary key all by itself).
Does this make sense?
If someone found useful the old example, I improved it and here is the new version:
It uses breeze internal validators.
I added an example on StackOverflow that may be useful to someone:
385 votesunder review · 21 comments · 1. BreezeJS Feature Suggestions · Flag idea as inappropriate… · Admin →
I've voted on this, but I also like more the tweaked version of Ward.