search

BlueHotDog / sails-migrations

The missing, migrations, arm of the octopus
MIT License
158 stars 37 forks source link

db:create fall in task 'createVersionTable #38

Closed pimenovoleg closed 9 years ago

pimenovoleg commented 10 years ago

Run

grunt db:create -v

//console output Running "db:setup" task

Running "db:loadConfig" task

Running "db:createVersionTable" task Verifying property migration.config exists in config...OK Creating version table Warning: Invalid connection name specified Use --force to continue.

But the Database is created.

Use Sails.js 0.10.4, sails-mysql 0.10.6

simplyb commented 9 years ago

I'm also running into this issue. For some reason connectionName is being passed to sails-mysql as the table name, which is sails_schema_migrations. I need to move on to some other things but will circle back to trying to diagnose this at some point this week.

simplyb commented 9 years ago

@Fost Were you able to work around this issue?

BlueHotDog commented 9 years ago

right, this is due to balderdashy/waterline issues and continues bugs and breaking changes I'm to the point of thinking about switching to some other data persistence layer, it will still integrate smoothly with sails, but the migrations will be written in a different language.(say sequelize) (this is after spending about 4 days debugging waterline) how do you guys feel about that?

simplyb commented 9 years ago

I've been wanting to switch off waterline for my application as well so I'm all for it.

BlueHotDog commented 9 years ago

hi guys, we've not forgotten you. still missing some tests, but feel welcome to give https://github.com/BlueHotDog/sails-migrations/tree/moving_to_knex a check

BlueHotDog commented 9 years ago

released a new version, should fix this.