Change Set 21512 - Conflict Resolution

April 24, 2007 13:01

A few template tweaks to address name conflicts, particularly:

  • Work Item 9789 - Foreign key and field properties with identical names in generated ActiveRecord

As part of this change, I've fully qualified the naming (i.e. included the namespace) in foreign table references generated by the class templates. This should help prevent potential naming conflicts across tables.

Download


4 Comments
Actions: E-mail | Permalink | Comment RSSRSS comment feed

Related posts

Comments

April 25. 2007 23:59

Justin M. Keyes

using(TransactionScope) still seems to fail if DTC isn't enabled. From the discussion in the work item at the URL below, I thought DTC wouldn't be required?

www.codeplex.com/.../View.aspx?WorkItemId=9516

I don't want to file a bug if I am mistaken.

Justin M. Keyes

April 26. 2007 01:09

Eric Kemp

Are you using it with the AutomaticConnectionScope? Without that, it will be promoted to the DTC...

Eric Kemp

April 26. 2007 17:30

Justin M. Keyes

I wrapped it in using(SubSonic.SharedDbConnectionScope) and it works. I thought I was only supposed to do that if I were changing connection strings on the fly. But it works now, quite amazing! Thanks!

Justin M. Keyes

April 26. 2007 20:12

Justin M. Keyes

Note: one cannot use AutomaticConnectionScope from outside the library because AutomaticConnectionScope is marked as "internal".

Using SubSonic.SharedDbConnectionScope around TransactionScope in my application, things seem to work fine (no DTC errors), but the code is not transactional. I have filed a bug report (work item 9906 ).

Justin M. Keyes

Comments are closed