Changes for page Using Model Groups

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+WOLips Tutorials

Content

...	...	@@ -1,5 +1,5 @@
1		-WOLips "finds" models just like NSBundle does (i.e. hunt and auto-include all the .eomodeld's). The problem with that behavior is that some people actually have multiple versions of the same model (they have OracleModel, FrontBaseModel, etc. instead of using prototypes **++**). But EOModelGroup's namespace has to be unique on model name and entity name, so that blows up with NSBundle-style "find everything".
	1	+WOLips "finds" models just like NSBundle does (i.e. hunt and auto-include all the .eomodeld's). The problem with that behavior is that some people actually have multiple versions of the same model (they have OracleModel, FrontBaseModel, etc. instead of using prototypes **++**). But EOModelGroup's namespace has to be unique on model name and entity name, so that blows up with NSBundle-style "find everything".
2	2
3		-EOModelGroup's in WOLips, consequently, let you define an explicit list of models to load into Entity Modeler. Then rather than open your model with Entity Modeler, you open your .eomodelgroup with Entity Modeler and it will avoid the conflict.
	3	+EOModelGroup's in WOLips, consequently, let you define an explicit list of models to load into Entity Modeler. Then rather than open your model with Entity Modeler, you open your .eomodelgroup with Entity Modeler and it will avoid the conflict.
4	4
5		-**++** this is a really, profoundly **bad** idea. Use prototypes.
	5	+**++** this is a really, profoundly **bad** idea. Use prototypes.