timestampable + versionable Behaviors produces unnecessary columns

[MattiasBiri]

If I applay both versionable and timestampable behavious to a table
the updated_at column is always the same as the created_at column.

This is obvious becouse every update is a new entity if we use versioning,
but in this case the updated_at column is unnecessary.

Not a very important thing, but with big databases it could be annoying...

[willdurand]

Heya, nice report, thanks.

@themouette did you use both timestampable, and versionable? It could be nice to tweak the behavior as @MattiasBiri suggested, isn't it?

[MattiasBiri]

I found that if you set both created_at and updated_at column name to the same, it will produces the created at column only.
So this is a tested workaround:

    <behavior name="versionable" />
    <behavior name="timestampable">
        <parameter name="create_column" value="created_at" />
        <parameter name="update_column" value="created_at" />
    </behavior>

[willdurand]

Well, I guess it's a nice workaround but the behavior should handle that :)