MoonStorm
MoonStorm
3.0 has a ton of changes so I'm just gonna manage this merge manually. Thanks a lot!
That insert into the temp table is indeed the problem for a timestamp/rowversion column, however the fix is not trivial. Removing that temp table and relying fully on the OUTPUT...
Don't need to do anything. Just watch the SQL statements in VS2015 while debugging normally. I believe they're showing in the IntelliTrace window, but I'm not 100% sure. I remember...
Yes, version 3.0 has introduced some breaking changes. In the area you mentioned, I believe the goal was to remove the informational properties in favor of the fluent registration methods....
That can be easily achieved by adding a config property in the config .tt file and using it inside the model generator .tt file. A pull request for this would...
Wow, thank you so much! I'll do some research to understand what it takes to add it to our test suite.
Thanks for sharing your work. I'm gonna try to find some time to review it. I have a couple of ideas myself to refactor the JOINs. We'll see what comes...
Discovered a lot of problems with the code after attaching tests to it so you might wanna check the changes we've made to your code for 3.1.
We just added support for this in 3.1 and added tests with combined scenarios of rowversion columns and triggers.