From: Paul H. <pa...@lo...> - 2015-01-23 01:49:28
|
Hi Larry, On 23 Jan 2015, at 11:45 am, Larry Mills-Gahl <el...@gm...> wrote: > I’m working on some migrations for other models and am finding that that model ends up in the migration queue even though it is listed in er.migration.skipModelNames > > I’m working through a couple of break points where ERXMigrator iterates through models and to get through a normal migration, I’m finding that I have to make the skipModelNames.contains() check in some additional places. > > I have a couple questions: > > Has anybody else run across this issue? This, or something like it, has definitely come up before. Matt Ness asked a very similar question on the list last July. I don't think that property is working as advertised. Matt, did you get to the bottom of it? -- Paul Hoadley http://logicsquad.net/ |