Best practice cfwheels with SQL Server: datetime, datetime2 or timestamp

[Thorsten Eilers]

What's Best practice for cfwheels with SQL Server 2012
To use datetime, datetime2 or timestamp?

[Andy Bellenie]

What for?

On 20 July 2012 16:11, Thorsten Eilers <thorste...@googlemail.com> wrote:

What's Best practice for cfwheels with SQL Server 2012
To use datetime, datetime2 or timestamp?

--
You received this message because you are subscribed to the Google Groups "ColdFusion on Wheels" group.
To view this discussion on the web visit https://groups.google.com/d/msg/cfwheels/-/lyDxgIKdMZwJ.
To post to this group, send email to cfwh...@googlegroups.com.
To unsubscribe from this group, send email to cfwheels+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/cfwheels?hl=en.

[Thorsten Eilers]

The default cfwheels date fields:
createdat
updatedat
deletetat

[Andy Bellenie]

I don't know about MySQL but I always use datetime in SQL Server

--
You received this message because you are subscribed to the Google Groups "ColdFusion on Wheels" group.

To view this discussion on the web visit https://groups.google.com/d/msg/cfwheels/-/nw6SIWhT8nQJ.

[Thorsten Eilers]

According to this thread datetime2 is more accurate and has a wider date frame and some other options.
http://stackoverflow.com/questions/1334143/sql-server-datetime2-vs-datetime

I think for my new app I will switch to datetime2. Just in case I will ever need this features.