ERXMigration skipModelNames problem?

Larry Mills-Gahl <[email protected]> Thu, 22 Jan 2015 20:15:58 -0500
Newsgroups gmane.comp.web.webobjects.wonder-disc
Message-ID <[email protected]>
--===============5798548372514714872==
Content-Type: multipart/signed;
	boundary="Apple-Mail=_87A76083-35D3-491A-913F-B7F8CC88E47D";
	protocol="application/pgp-signature"; micalg=pgp-sha1


--Apple-Mail=_87A76083-35D3-491A-913F-B7F8CC88E47D
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_12F1E95A-B5C6-4125-B465-E6C8B43FE09C"


--Apple-Mail=_12F1E95A-B5C6-4125-B465-E6C8B43FE09C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hello,

I have an odd (non-default) setup where I remove a model from the =
default model group when my EO framework is loaded.

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

I=E2=80=99m working through a couple of break points where ERXMigrator =
iterates through models and to get through a normal migration, I=E2=80=99m=
 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?

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.

Any thoughts or comments or land mines to avoid?

Larry Mills-Gahl
[email protected]







--Apple-Mail=_12F1E95A-B5C6-4125-B465-E6C8B43FE09C
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"">Hello,<div class=3D""><br class=3D""></div><div class=3D"">I =
have an odd (non-default) setup where I remove a model from the default =
model group when my EO framework is loaded.</div><div class=3D""><br =
class=3D""></div><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&nbsp;<span style=3D"color: rgb(47, =
175, 169); font-family: Monaco; font-size: 11px;" =
class=3D"">er.migration.skipModelNames</span></div><div class=3D""><br =
class=3D""></div><div class=3D"">I=E2=80=99m working through a couple of =
break points where ERXMigrator iterates through models and to get =
through a normal migration, I=E2=80=99m finding that I have to make the =
skipModelNames.contains() check in some additional =
places.&nbsp;</div><div class=3D""><br class=3D""></div><div class=3D"">I =
have a couple questions:</div><div class=3D""><br class=3D""></div><div =
class=3D"">Has anybody else run across this issue?</div><div =
class=3D""><br class=3D""></div><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.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Any thoughts or comments or land mines =
to avoid?</div><div class=3D""><br class=3D""><div =
apple-content-edited=3D"true" class=3D"">
<div style=3D"color: rgb(0, 0, 0); font-family: Helvetica;  font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " =
class=3D""><div style=3D"color: rgb(0, 0, 0); font-family: Helvetica;  =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
-webkit-auto; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " =
class=3D""><div class=3D"">Larry Mills-Gahl</div><div class=3D""><a =
href=3D"mailto:[email protected]" =
class=3D"">[email protected]</a></div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div></div><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_12F1E95A-B5C6-4125-B465-E6C8B43FE09C--

--Apple-Mail=_87A76083-35D3-491A-913F-B7F8CC88E47D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJUwaDOAAoJEH6+KDQxPmwvKgcH/3cC3O5q/Q9CmtlhfLC1UCqb
RaTWmxM9L7MXpmgjov63rSBBOKAMSr9+7fNv1qLBgKxGJD71HZdzm/2hV/LqGpVu
5O6damb6Cs/M01g/fjvJZD9heQ7iX6u6IyvblY4+l527crRRS7HVXliRiKeOfoz/
wCJsybKvs12Ph8jHm0JeJAS4Bx7FPU7iQtBtNxd1I8YDHuWv+Yp3QJ1mP8nf9C34
diiOTeuawtXJUiS40gn2DOKNZPkaCjtmSHXXNKejSefQK67t8MGPAUJT/hQFowS/
0IjbCS6FQnJCb0SxUQq3WNeugWd5uMK6zh8Ydz0pBJpRLPzOEerFHNz0mrfmcgo=
=nbBV
-----END PGP SIGNATURE-----

--Apple-Mail=_87A76083-35D3-491A-913F-B7F8CC88E47D--


--===============5798548372514714872==
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
--===============5798548372514714872==
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

--===============5798548372514714872==--