The idea is to have two fields: created and modified, with timestamps when object is created, and last modified

Submitted by chris melman on 31 August 2012 at 15:57

those fields are added in last commit including tests

Nice! Can you also add this to documentation on webdsl.org? And what happens with legacy code that already adds those fields explicitly? Can the fields be removed and will the same db columns be used?

I will add it to the documentation on webdsl.org. About the legacy code, it will give an error on the fields, Danny said that if the columns have the same type (DateTime) it should be no problem removing them. However didn’t had an app where this could be tested locally

You mean, the compiler/IDE will give an error on the field? Perhaps that could be a warning if they are actually DateTime fields. I have applications that use this; will test.

Yeah indeed the compiler/IDE will give an error on the field. I guess a warning is not fatal to the compiler and could probably end up having problems in the compiler when the property is specified more than once.

But if it is the exact same property, the duplication can be ignored, which would be helpful for legacy applications. I would like to test this first before I remove all the created/modified fields from my apps.