These are chat archives for db-migrate/node-db-migrate

22nd
Oct 2015
Eric Lin
@ericln
Oct 22 2015 00:05
sure will do, i was just wanting to get a sense of what do-migrate can do / or meant to do first :)
Eric Lin
@ericln
Oct 22 2015 00:12
@wzrdtales data manipulation or just migration: well, to me migration will include some sort of data manipulation along with some schema change etc?
Tobias Gurtzick
@wzrdtales
Oct 22 2015 12:22
@ericln to be exact, a schema change is indeed a bit different for noSQL schema, but really ment data manipulations like: create a new column and then populate this column with data from column a and b. This would'nt be really in the context of a migration anymore.
Eric Lin
@ericln
Oct 22 2015 16:35
@wzrdtales really..that’s interesting, by no mean i have a lot experience in this, but where would that fit tho?
Tobias Gurtzick
@wzrdtales
Oct 22 2015 20:00
everything not structure related is some kind of data transformation and will be handled as "seeder" within db-migrate in the future. a migration only contains the structure change normally not any data operations that may exist. I worked already in many projects where the usage and abuse of migrations to use them to do such data manipulations just turned out to be very unstructured. There are times when you want to execute structure changes without applying the data manipulations and there are times you want both. And mixing those two things together ends up in a mess.
I'm currently working on the docs to all those things, you may have a look at them when I push them (I can notify you if you want), that should give a better idea of the whole thing.
Eric Lin
@ericln
Oct 22 2015 22:17
Not too sure i feel the same for separating structure and data migration. But it’ll be nice to read a bit more on this topic once you are done with the doc :) thanks