Re: Compound primary key is being generated - contradicts documentation?

On 21/dic/04, at 06:30, Tony Copping wrote:

> [...]
>   The compound keys worked as expected when they were both strings. I 
> supplied a string identifier for the "classification" and a unique 
> identification id within that classification, and WebObjects didn't 
> bother trying to generate a key for me. Now I changed the model to 
> directly associate the objects within a classification to an object 
> with other information for the classification. I still set my own 
> unique identifier (a string), but now the EOF decides to assign a 
> unique id of its own  (overwriting my setting). Does anyone know why 
> it does this, or if there is a way to make it stop?

Have you checked your propagate primary key settings?



Hope this helps

--
Giorgio Valoti
--------------