Okay, I think I am ready to submit this for team review (and hopefully inclusion). This patch is generated against Revision 551. Here is an overview of what's in this patch:
NOTE: There is still a bug with the unit tests when it comes to objects that have child objects of the same type (i.e. you have a User object Employee that has a property called Manager which is of type User) and where that table has a unique constraint one one or more columns. The reason is that the test data is randomly generated at code-generation time, and so is the same for the Employee and Manager instances. When it comes time to DeepSave the Employee, the Manager isntance throws a SQL exception for the unique constraint violation. The solution is to generate the random data at run-time. I have the functions/mechanism to do this for strings. Once I have it done for the other data types, I will submit a separate patch.
Please let me know if you find any issues.
Great work Tony!
As there's quite a lot here and on your other patch I've started a discussion with the other team members to see how we can progress these.
Hopefully we'll be able to get things moving on it.
swin
Sounds good, swin, thanks.
I should point out that I am continuing to fix & refactor items related to mapping.config and other functions I "trip across" in the templates. Would it help if I were to generate a single patch that included both of my previous patches and my changes in the last day? I am running through debugging to eliminate compilation errors now.
Tony
SVN is pretty smart in working out how to merge code. Make a patch of everything that has changed. Then edit your first post in this thread and change the file to your new patch. Don't forget to rename test.patch to test.patch.text
Regards Taliesin
There's your combined patch for mapping.config and EntLib3, both against rev 552. You still need to make sure you create the file & directory changes to the "References" directory.
Let me know if I can help!
Good work, thanks Tony!
Patched in at version SVN554
This patch breaks the Alieases file, it totally disregards all entries in the Aliases file. Needless to say, it just generated most of my entities with the wrong name, which is a royal pain in the ass. Now I have to go manage the mapping.config file for each entity, for every column??
There is a known problem with the pascal casing routine introduced with this update. I've posted a suggested fix but I was awaiting feedback from the original contributor to make sure it worked with his db.
see http://community.codesmithtools.com/forums/24441/ShowThread.aspx#24441
if I don't get any response back by tomorrow I'll post what I think will fix it.
hth
swin,
I don't see a patch that will CORRECTLY fix the field name casing issues. Right now my field names are all screwed up, I have a statusId field in my table and the property name used to be StatusId, which I loved, now it's statusid (which I HATE).
Do you have a fix for this? If so, can you please post a patch for it?
My comments are in no way a reflection of anyone's views but my own.
Lighten up. It's an open-source development project being worked on by the grace of contributors and the hard work of the core team. If you aren't prepared to contribute to the fix directly, try offering constructive feedback with details of what it's doing wrong where. If you can't do either of those things, go back to the version that was working for you and simply go on with your project.
Your inconsiderate use of text formatting and unconstructive, demanding feedback does nothing but promote the incorrect idea that the work of the NetTiers team is not appreciated or that the efforts of contributors attempting to give back to the product that has made their lives easier are unwelcome.
Swin and Tony,
sorry if I came on as a demanding ***, that wasn't my intention at all. Upon re-reading my post, I can see I should have been more considerate in my use of language and casing. All I was trying to do was to express what's not working for me, and kindly request a patch, IF one exists.
That's not what my previous post conveyed, for that I apologize, I appreciate this project and everyone working on it more than I can convey in a posting such as this, so please excuse my previous post.