Compatibility with storage configuration v4(r7384)
fixed wrong number of arguments for parser.writeInt
used package.json description and version so to avoid repetition and wrong information on Connect.js and DbOpen.js
Merge pull request #90 from ffissore/master

package.json version and description, wrong writeInt args, missing err handling
introducing underscore: replaced all our parser.is* and parser.mergeHashes
adding support to fetch plans to record load
still missing them in commands
Merge pull request #91 from ffissore/master

underscore and fetch plans
tiny improvements in RecordLoad
next release will be 0.9.7
fetch plans now working even with commands #85
spread "use strict" and fixed a handful of warnings
added DbOpen.readClusterConfig
set "lengthInBytes" to zero when empty/null string comes from db
Merge branch 'storage_configuration_v4_compatibility' of git://github.com/Volune/node-orientdb into Volune-storage_configuration_v4_compatibility
testing merge from #88
fixed a failing test with new "status" field in class OUser now mandatory
now we are 1.2.x and 1.3.x compatible
fix: when both callback and options are missing from db.command, an error occurs
closes #92: incorrectly dividing and multiplying by 1000 in dates (de)serialization
see #95: using date() function (orientdb side) to make orient store a date with sql commands
fixes #96
Command.js:
- moved "subcontents" up 1 level, now son of result instead than result.content
- in case of single record, result.content is an array of one element
db.js:
- unified result.content management, now three cases can be handled with the same for loop
- processResult now requires 2 args, content and subcontents
fetch_plan.js:
- wrapped the test around another call to prepareDatabase so to have a richer database to query and to test what happens when mupliple records are returned
closes #92