data-import
data-import copied to clipboard
stmichael
sequel based dsl to migrate data from a legacy database to a new home.
@stmichael I think we could refine the README a bit. Adding a proper index at the top for example, because the README is quite long.
Just a suggestion, but since I needed it anyway I made a pull-request out of it: Let's give the option to enable and disable platform/database specific tests. Why? For me,...
You might want a few more unit tests, and there's a possibility this doesn't cover all execution contexts - though it meets all mine. I've added a new acceptance spec.
Now both definitions (simple and script) need the lookup tables. We need to find a better internal solution.
I started by decoupling the lookup tables from the definitions. It's not finished yet. There is still code that uses lookups on definitions. @senny what do you think about it...
We have a lot of data normalization to do in our migration. It would be very helpful to be able to extend the `ExecutionContext` of the mappings. I think we...
Hi, I'm really enjoying using this library, makes my life easier. One thing I'm not sure though, is if any "merge" mode exists, because default or :unique create new records...
As a goodie it would be extremely useful to be able to get the mapping any time after the import. Working with an imported database you often have the situation...
Our mapping file is getting big and we got some tables with a lot of mappings. The performance degraded massively when we added more and more mappings per table. I...