So EM DOES actually appear to "layer" them ... and it looks like the
real EOModel.createPrototypeCache does some amount of this also:
adaptor-custom prototypes, then EOPrototypes, then EOJDBCPrototypes.
At least that's how it LOOKS. I think the actual problem is that SQL
generator doesn't have all of Project Wonder's magic to make this all
work right with EOJDBCFrontBasePrototypes-style naming -- it's got
just an approximation of it. One of the things that's sacrificed is
prototype inheritance it would appear.
ms
On Apr 23, 2007, at 1:31 PM, Chuck Hill wrote:
> EOF does not do prototype inheritance so Entity Modeler should not
> either. It does seems to have some prototype caching oddities,
> perhaps that is what you are seeing?
>
>
> On Apr 23, 2007, at 12:10 AM, Lachlan Deck wrote:
>
>> Hi there,
>>
>> If you've got a model (MyEOJDBCPrototypes) with the following
>> entities: EOJDBCPrototypes, EOJDBCMySQLPrototypes etc
>>
>> Am I correct in assuming that the MySQL prototypes, for example,
>> need only specify what's not properly supported for that db?
>>
>> e.g., I have a prototype called 'clob' which in the base
>> prototypes maps to an external type of 'CLOB', but for the MySQL
>> one maps to LONGTEXT.
>>
>> That seems to look right within the Entity Modeler (when using
>> prototypes elsewhere) - however when I go to generate SQL it
>> complains about not knowing what to do with CLOB. i.e., it's
>> seemingly ignoring the mysql specific prototypes.
>>
>> Have I missed something or is this a bug in EntityModeler?
>>
>> with regards,
>> --
>>
>> Lachlan Deck
>>
>>
>>
>>
>
> --
>
> Practical WebObjects - for developers who want to increase their
> overall knowledge of WebObjects or who are trying to solve specific
> problems.
> http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
This archive was generated by hypermail 2.0.0 : Mon Apr 23 2007 - 13:42:30 EDT