AnantLabs / codesmith

Automatically exported from code.google.com/p/codesmith
1 stars 0 forks source link

PLINQO: Audits, MultipleResults, Broken Rules, ToString additions #55

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I attach modified version of PLINQO templates we are using for our
projects, please take a look and merge any changes you think should be
merged into project.

1. Modified Linq Audit with composity key support
(http://www.codeplex.com/DoddleAudit)
2. Enum fix (using Description for name rather name)
3. MultiResults unique results
4. ToString() method
5. Broken rule object details

Original issue reported on code.google.com by kachalkov on 13 Feb 2009 at 12:23

Attachments:

GoogleCodeExporter commented 9 years ago
Hi, 

Thanks for your addition.  We're reviewing your changes and will merge in what 
will
be good additions for everyone.

~ Paul

Original comment by paul.wel...@gmail.com on 19 Feb 2009 at 2:51

GoogleCodeExporter commented 9 years ago
We've added audits to the latest nightly build.  We implemented it differently
however.  Thanks for the contribution.

Original comment by paul.wel...@gmail.com on 9 Mar 2009 at 2:35

GoogleCodeExporter commented 9 years ago
Thanks Paul, appreciate that, I also noticed that Multi result is included into
latest build, but I can see that result sets are not unique, that mean because 
for
some reason this feature is not included into CodeSmith SQL Server schema 
provider
then we end up with 3-6 result classes which are the same.

Also, would be great if you can include ToString() method and broken rule
modifications as well as 

Original comment by kachalkov on 10 Mar 2009 at 2:56

GoogleCodeExporter commented 9 years ago
Breaking rule is not very infomative at this moment if multiple object breaks 
during
Submit changes

Original comment by kachalkov on 10 Mar 2009 at 2:57

GoogleCodeExporter commented 9 years ago
Good idea on the duplicate result sets.  We will get that corrected.

Can you please provide more information about what you would like to see from 
the
ToString() and what is missing from the broken rule message?

Original comment by ejsm...@gmail.com on 10 Mar 2009 at 3:26

GoogleCodeExporter commented 9 years ago
Thank, Eric, that would be great.

Right, basically, if you look into attachment there is a modified version of
\CSharp\Internal\Entity.Generated.cst which has ToString() method which I 
originally
found in NetTiers templates.

Broken rule message in current version of PLINQO works great except that 
sometimes
when you have multiple changes to the database and couple of the rules in 
different
object fails then this is not quite obvious to find out which one failed 
exactly, I
understand that this could be also bad design of the application, but I found 
it very
useful to have additional information about object failed using the following 
tiny
change of BrokenRuleException.cs:

                sb.AppendLine(rule.Context.TrackedObject.Current.ToString());

Another thing which would be nice to fix is CodeSmith.Data assembly does not 
have
[assembly: CLSCompliant(true)]

And I can say that we love PLINQO, tons of our blood was saved and many thanks 
for
the great tool like CodeSmith (if you could fix activation over proxy then it 
would
be unbeatable! ;)

Thank you very much again and keep doing such a great job!

Original comment by kachalkov on 10 Mar 2009 at 11:02

GoogleCodeExporter commented 9 years ago
I have implemented a generic ToString method on the entitybase so you can 
override
them in each entity if you wanted to.  I have also added the call to ToString 
in the
BusinessRuleException.  The CLSCompliant attribute is added as well.

Original comment by ejsm...@gmail.com on 12 Mar 2009 at 3:54

GoogleCodeExporter commented 9 years ago
Thanks, I looked into ToString implementation and just wonder why would you like
reflection implementation against generated one?

Original comment by kachalkov on 12 Mar 2009 at 10:57

GoogleCodeExporter commented 9 years ago
So it can be in the base class.  Otherwise you can't override it in your 
entities if
you don't want the default behavior.

Original comment by ejsm...@gmail.com on 13 Mar 2009 at 12:02

GoogleCodeExporter commented 9 years ago

Original comment by shannon....@gmail.com on 7 Oct 2009 at 3:53

GoogleCodeExporter commented 9 years ago

Original comment by shannon....@gmail.com on 30 Dec 2009 at 5:43

GoogleCodeExporter commented 9 years ago

Original comment by shannon....@gmail.com on 30 Dec 2009 at 6:03

GoogleCodeExporter commented 9 years ago
Guys, I'm checking PLINQO v4.0 and it still generates multiple results sets for 
the
stored procedures for our project which was fixed in my patch, please check out
attached for the DbmlGenerator.cs

Original comment by kachalkov on 5 Mar 2010 at 12:38

Attachments: