I'm not sure that modifying the plugins to use a UserInfo dictionary entry would be more likely to cause problems than modifying them to use a new top-level entry.
There is already a _entityModeler key that is added to the various UserInfo dictionaries to hold things like multiple connection dictionaries and modelDoc that are additions to the apple-published spec. With that said, in this particular situation it seems more likely that the individual plugins should be modified to deal with multiple components in the table name. As you noted, different DBs have different levels of organization available. Schemas, Table Spaces, Databases, OracleWhatzit, etc. simply adding a key for schema is an oversimplification that begs for misuse (most likely by me). Dave Sent from my iPhone > On May 4, 2015, at 8:04 PM, Ângelo Andrade Cirino <[email protected]> wrote: > > I thought about it too, but it would be a non-standard solution, since each > developer could use a name for the property. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
