No enum constant com.orientechnologies.orient.core.metadata.schema.OType.NUMBER

**Node version**:
**Sails version** _(sails)_: 1.2.3
**ORM hook version** _(sails-hook-orm)_: 2.1.1
**Sockets hook version** _(sails-hook-sockets)_: ^2.0.0
**Organics hook version** _(sails-hook-organics)_: ^0.16.0
**Grunt hook version** _(sails-hook-grunt)_: ^4.0.0
**DB adapter & version** _(e.g. sails-orientdb)_: 0.10.60

OrientDB Version: 3.0.25
Java Version: 1.8.0_232
OS: Ubuntu 18.04.3
orientjs version ^2.2.1
Using OrientDB docker image latest

Expected behavior
Migrations are supposed to run smoothly

Actual behavior
Database and tables get created but fails at some step giving following error:

`{ OrientDB.RequestError: No enum constant com.orientechnologies.orient.core.metadata.schema.OType.NUMBER at child.Operation.parseError (/home/kaustubh/Development/test-project/node_modules/orientjs/lib/transport/binary/protocol33/operation.js:905:13) at child.Operation.consume (/home/kaustubh/Development/test-project/node_modules/orientjs/lib/transport/binary/protocol33/operation.js:496:35) at Connection.process (/home/kaustubh/Development/test-project/node_modules/orientjs/lib/transport/binary/connection.js:459:17) at Connection.handleSocketData (/home/kaustubh/Development/test-project/node_modules/orientjs/lib/transport/binary/connection.js:331:20) at Socket.emit (events.js:198:13) at Socket.EventEmitter.emit (domain.js:448:20) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:269:11) at Socket.Readable.push (_stream_readable.js:224:10) at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17) name: 'OrientDB.RequestError', message: 'No enum constant com.orientechnologies.orient.core.metadata.schema.OType.NUMBER', data: {}, previous: [], id: 1, type: 'java.lang.IllegalArgumentException', hasMore: 0 }`

Start by reproducing the migration with the listed Sails, sails-orientdb, OrientDB, and orientjs versions, then inspect the stack-trace entry points in node_modules/orientjs/lib/transport/binary/protocol33/operation.js and connection.js. Done means migrations complete successfully without the OType.NUMBER error and the compatible version or required change is documented.

Written by the indexing model from the issue text.