Yes. Unless we can intercept on initial record parse. A user wouldn't have
use for an object as much as a string. Would be even better if the detail
was a string. If there is an earlier interception, where would you
recommend? What are the use cases for an object with cluster and position?

It will be needed to return a string in db.query, db.record.get, etc.
On Apr 3, 2014 8:27 AM, "Charles Pick" <notifications@github.com> wrote:

> In lib/db/index.js:
>
> > @@ -189,6 +190,9 @@ Db.prototype.exec = function (query, options) {
> >   * @promise {Mixed}          The results of the query / command.
> >   */
> >  Db.prototype.query = function (command, options) {
> > +	options = options || {};
> > +	options.class = options.class || 'com.orientechnologies.orient.core.sql.query.OSQLSynchQuery';
>
> i think this should be defined in protocol/operations/command.js<https://github.com/codemix/oriento/blob/master/lib/protocol/operations/command.js#L11>instead of here, and are we really sure it should be a default for every
> query?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/codemix/oriento/pull/6/files#r11248956>
> .
>