If the entity is storing the db value and the current value, then why return isDirty = true if a single field is changed and then changed back to the original value?

I just noticed that there is a sql update for this case and am just wondering why...

The Update is executed only if something id dirty (some field has been changed). Could you confirm that?

static void Main(string[] args)
        {
           SomeEntity entity = SomeEntityManager.GetByPK(1111111111);
            int original = entity.SomeIntField;
            entity.SomeIntField = original + 1;
            entity.SomeIntField = original;

            Console.WriteLine(entity.IsDirty);

            EntityUtilities.Save(entity);
            Console.ReadLint();
}

The console output is true and an update statement is executed.

Same discussion I think: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=10017

Yes same discussion, thanks for the link. I understand the events argument, but I don't really mind if the Save button (see linked post) is disabled again when the entity becomes "clean", I just don't want the database call. Let them click save all they want, (it even probably makes sense to let them "think" they are saving again because they did make a "change"), because when the framework looks at the entity it would know that there was no need for a database hit.

Thanks again, I'm continually impressed with this forum in that you guys will entertain any question regardless of whether it was covered last week or 3 years ago...keep up the good work and I'll keep pushing the use of LLBLGen on all my projects.

Thanks for the kind words