You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since DateTime precision is required based on business requirements, programmers sometimes need to store DateTime values with different precisions.
In line number 70 of QueryBuilder/SqlResult.cs, the code "<< return "'" + date.ToString("yyyy-MM-dd HH:mm:ss") + "'"; >>" causes all datetimes to be stored with second precision, which may cause issues for certain business scenarios.
I recommend using "<< return "'" + date.ToString("yyyy-MM-dd HH:mm:ss.FFFFFFF") + "'"; >>" instead, which delegates the DateTime precision serialization to the input value that can be changed by the end developer during Insert and Update commands.
I made these changes for myself, and my problems were easily resolved.
Perhaps this discussion will improve this project.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Since DateTime precision is required based on business requirements, programmers sometimes need to store DateTime values with different precisions.
In line number 70 of QueryBuilder/SqlResult.cs, the code "<< return "'" + date.ToString("yyyy-MM-dd HH:mm:ss") + "'"; >>" causes all datetimes to be stored with second precision, which may cause issues for certain business scenarios.
I recommend using "<< return "'" + date.ToString("yyyy-MM-dd HH:mm:ss.FFFFFFF") + "'"; >>" instead, which delegates the DateTime precision serialization to the input value that can be changed by the end developer during Insert and Update commands.
I made these changes for myself, and my problems were easily resolved.
Perhaps this discussion will improve this project.
Beta Was this translation helpful? Give feedback.
All reactions