db-migrate/db-migrate-base

Not able to run db-migrate up

Closed this issue · 0 comments

I am trying to run the db-migrate up and getting this error.

[ERROR] Error: not implemented at Object.runSql (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/db-migrate-base/index.js:496:11) at /Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/db/migration/mongodb/scripts/20170612183925-test.js:32:15 at tryCatcher (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/promise.js:693:18) at Async._drainQueue (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/async.js:133:16) at Async._drainQueues (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues (/Users/ahmedwasfy/Documents/sears/PIT/ca.sears.intelligence.price/server/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:672:20) at tryOnImmediate (timers.js:645:5) at processImmediate [as _immediateCallback] (timers.js:617:5)

here is my config

{ "dev": { "driver": "mongodb", "database": "dev", "host": "localhost", "sql-file": true, "multipleStatements": true }, "test": { "driver": "mongodb", "database": "test", "host": "192.168.33.10", "sql-file": true, "multipleStatements": true } }
Is that a bug or am I missing a config ?