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...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to a...