Sails version: 1.1.0
Node version: 11.4.0
NPM version: 6.4.1
DB adapter name: sails-mongo
DB adapter version: ^1.0.1
Operating system: Mac OS
Also, it used to work fine until I migrated to v1 (from v.012). Now fixed this for myself, changing forge-stage-three-query.js to processed not known fields.
https://github.com/balderdashy/sails/issues/4105 and https://trello.com/c/b57sDgVr/124-adapter-spec-change-to-allow-for-more-flexible-base-values seem related.
Hi @solovieff! It looks like you missed a step or two when you created your issue. Please edit your comment (use the pencil icon at the top-right corner of the comment box) and fix the following:
As soon as those items are rectified, post a new comment (e.g. “Ok, fixed!”) below and we'll take a look. Thanks!
*If you feel this message is in error, or you want to debate the merits of my existence (sniffle), please contact [email protected]
Ok, fixed!
@solovieff Thanks for posting, we'll take a look as soon as possible.
For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her minions in Austin, click here.
Same problem here and exactly same configuration:
Sails version: 1.1.0
Node version: 11.4.0
NPM version: 6.4.1
DB adapter name: sails-mongo
DB adapter version: ^1.0.1
Operating system: Mac OS
@solovieff @saccodd
I was also able to reproduce this issue:
(TypeError: Cannot read property 'columnName' of undefined)
with the same configuration and versions.
We welcome a PR for sails-mongo if anyone is wanting to offer a patch.
Most helpful comment
Same problem here and exactly same configuration:
Sails version: 1.1.0
Node version: 11.4.0
NPM version: 6.4.1
DB adapter name: sails-mongo
DB adapter version: ^1.0.1
Operating system: Mac OS