Skip to main content

A DD4T.net Implementation - Model Comparators

If you remember the post String Typed Models, I was mentioning that class ModelBase was implementing the IComparable generic interface.

    public class ModelBase : IComparable<ModelBase>


The reason for doing so is to be able to easily compare two implementation of ModelBase. This is especially useful when we need to sort models or put them in some kind of sorted collections.

For example, when building ISet collections of models, we need to either have the set populated with objects that implement IComparable or provide an external comparator.

When implementing the IComparable, we need to implement the CompareTo method. I decided to compare two ModelBase objects by comparing their Id (which is their TcmUri). In other words, two models are the same, if they have the same TcmUri.

    public int CompareTo(ModelBase other)
    {
        if (other == null)
        {
            return 1;
        }

        string otherId = other.Id;

        if (Id == null && otherId == null)
        {
            return 0;
        }
        else if (otherId == null)
        {
            return 1;
        }
        else if (Id == null)
        {
            return -1;
        }

        return Id.CompareTo(otherId);

    }

A slightly different scenario is when we need to put a ModelBase in a ISet implementation, such as HashSet. In this case, the extremely confusing equality framework of .net can be summarized by simply overriding the default GetHashCode() and Equals(object) methods. There will be no other requirements such as implementing IEquatable or IEqualityComparer, etc. The code below illustrates the overridden implementations:

    public override int GetHashCode()
    {
        return Id.GetHashCode();
    }

    public override bool Equals(object other)
    {
        if (other == null || !(other is ModelBase))
        {
            return false;
        }

        string otherId = ((ModelBase)other).Id;

        if (Id == null && otherId == null)
        {
            return true;
        }
        else if (otherId == null || Id == null)
        {
            return false;
        }

        return Id.Equals(otherId);

    }


Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven