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
Tell about how DATE/DATETIME fields are parsed in node-cubrid. The values are parsed as UTC values. That is if the data in date field is stored as 10/02/2012, when it is returned by node-cubrid, it is returned in local time as Tue Oct 02 2012 09:00:00 GMT+0900 (KST). This example consider my current time zone +09:00. This is done because CUBRID does not store the time zone information along with the date. So we suggest storing dates in UTC consistently.
Some methods will be removed in v3.0.0.
The text was updated successfully, but these errors were encountered:
New Features
#49 Implement Protocol v6 of CUBRID.
#13 Add support for alternative hosts to support client side HA.
#12#11 Provide a configurable logging function.
#18 Added ENUM data type support via the old protocol.
#14 Support promises.
Refactoring
#48 Update README.
#14 Indent using spaces instead of tabs.
#14 Reduce the use of self where this can be used directly.
#14 Extract constants and other useless variables from the connection
object.
DATE
/DATETIME
fields are parsed innode-cubrid
. The values are parsed as UTC values. That is if the data in date field is stored as10/02/2012
, when it is returned bynode-cubrid
, it is returned in local time asTue Oct 02 2012 09:00:00 GMT+0900 (KST)
. This example consider my current time zone+09:00
. This is done because CUBRID does not store the time zone information along with the date. So we suggest storing dates in UTC consistently.v3.0.0
.The text was updated successfully, but these errors were encountered: