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 v3.0.0 the drive will communicate using the same protocol defined in the target CUBRID Broker. The version is determined right after the connection with Broker is established and the Broker tells us which version it speaks in by default.
In cases when new CUBRID versions are released which speak in new protocols, node-cubrid will speak with them using the latest protocol it knows. At this moment it is v6.
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.
Though CUBRID Broker supports old protocols, the new protocols provide more features and perhaps performance improvements in network communications.
The default protocol versions are listed below:
v7
.v6
v5
v4
v3
v2
v1
node-cubrid
v2
uses Protocolv1
to connect to all versions of CUBRID. We need to add support all protocols up tov6
.The text was updated successfully, but these errors were encountered: