Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
While there’s lots to like about DataObjects.NET, I’ve found help resources to be a lean, and can’t find a solit example of using DataObjects.NET with RDBMS generated primary keys. It would seem as though D4O won’t do inserts against SQL Server unless it’s in controll of the key.
Has anyone solved this in the wild?
There is no easy way to make DO4 use IDENTITY columns – mainly, because it is designed to rely on bulk key generation (aka HiLo algorithm).
AFAIK, there are no good workarounds here. E.g. DO4 supports custom key generators, but it’s pretty complex to develop one relying on IDENTITY column – in fact, it should insert fake records in bulks and remove them further (or rollback a transaction) to work. Taking into account there can be columns with unique constraints, the task becomes pretty complex.
We’ll think about implementing this in future.