Sanjay,
I am sorry, that I have to disagree, but I spent some time on this subject when evaluating options to implement DST support in the core for DNN 5.x.
Most modules - even in the core - deal incorrectly with timestamp values by usually deriving it from SQL Server using GetDate. There are several issues caused by this practice:
- timestamps will remain unchanged, when server time zone is changed (e.g. for DST turned on/off)
- there might be differences between sql server and web server time, and any comparison with current time on the web server will be inacurate (e.g. for search indexing)
- timestamp in "createdAt" field, autmatically set in AddItem stored procedure cannot be kept during Export/Import
Therefore my advice to all module developers:
- Always store timestamp values in UTC and convert to appropriate user time zone when displaying the value to the user. Due to current limitations of DotNetNuke, the time displayed will be offsetted by an hour during DST.
- Always create timestamp on the web server and pass to SQL to avoid inaccuracies and be able to keep it
The issues listed are of minor relevance for Feedback module, but should be regarded as best practices.