Re: ERXMigration skipModelNames problem?
Dennis Bliefernicht <[email protected]> Fri, 23 Jan 2015 08:52:13 +0100
| Newsgroups | gmane.comp.web.webobjects.wonder-disc |
|---|---|
| Message-ID | <[email protected]> |
--===============6414073701205168501== Content-Type: multipart/alternative; boundary="Apple-Mail=_14CB4268-B639-4ECF-9EE0-FAC9CBE40FC6" --Apple-Mail=_14CB4268-B639-4ECF-9EE0-FAC9CBE40FC6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, > I=E2=80=99m 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 Do you happen to have dependencies between the models, i.e. modelB = (which still should be migrated) uses entities from modelA (which is in = skipModelNames)? We noticed that in these cases modelA will still be = migrated as a dependency of modelB. > Does anybody with more detailed knowledge of ERXMigrator see a problem = with checking skipModelNames in _buildDependenciesForModel? It looks = like that is the place where models are placed in the migrations map and = it still works after I removed the other skipModelNames checks that I = added in drilling through the stack traces.=20 That is actually what we ended up doing as well. On the one hand now the = property works as advertised, on the other hand you are always in danger = of having migrated to the latest version of modelB which still will not = work, because modelA is not up to date. Worse even, if they are sitting = in the same database, migrations of modelB may fail because constraints = cannot be set up properly. This change, while fine in certain = circumstances, is possibly not good enough for a generic use-case = because of these side-effects though? On the other hand, when you=E2=80=99= re using skipModelNames you=E2=80=99re probably already somewhat aware, = that you might run into issues if you=E2=80=99re not knowing exactly, = what the specific migrations do... Greetings Dennis= --Apple-Mail=_14CB4268-B639-4ECF-9EE0-FAC9CBE40FC6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">Hi,<div class=3D""><br class=3D""><div><blockquote = type=3D"cite" class=3D""><div class=3D"">I=E2=80=99m 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 <span class=3D"" = style=3D"color: rgb(47, 175, 169); font-family: Monaco; font-size: = 11px;">er.migration.skipModelNames</span></div></blockquote><div><br = class=3D""></div><div>Do you happen to have dependencies between the = models, i.e. modelB (which still should be migrated) uses entities from = modelA (which is in skipModelNames)? We noticed that in these cases = modelA will still be migrated as a dependency of modelB.</div><div><br = class=3D""></div><div><blockquote type=3D"cite" class=3D""><div = class=3D"">Does anybody with more detailed knowledge of ERXMigrator see = a problem with checking skipModelNames in _buildDependenciesForModel? It = looks like that is the place where models are placed in the migrations = map and it still works after I removed the other skipModelNames checks = that I added in drilling through the stack = traces. </div></blockquote><div class=3D""><div class=3D""><br = class=3D""></div></div><div class=3D"">That is actually what we ended up = doing as well. On the one hand now the property works as advertised, on = the other hand you are always in danger of having migrated to the latest = version of modelB which still will not work, because modelA is not up to = date. Worse even, if they are sitting in the same database, migrations = of modelB may fail because constraints cannot be set up properly. This = change, while fine in certain circumstances, is possibly not good enough = for a generic use-case because of these side-effects though? On the = other hand, when you=E2=80=99re using skipModelNames you=E2=80=99re = probably already somewhat aware, that you might run into issues if = you=E2=80=99re not knowing exactly, what the specific migrations = do...</div><div class=3D""><br class=3D""></div><div = class=3D"">Greetings</div><div = class=3D"">Dennis</div></div></div></div></body></html>= --Apple-Mail=_14CB4268-B639-4ECF-9EE0-FAC9CBE40FC6-- --===============6414073701205168501== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet --===============6414073701205168501== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Wonder-disc mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wonder-disc --===============6414073701205168501==--