If you look at some of the model I sent you earlier there are example
except that the EOModeler UI is awkward. We have developed the code
to abstract index generation in EOF with plug-in per database.

Pierre
On 19-Jul-06, at 2:00 PM, Mike Schrag wrote:
> Interesting .. So you have a "list of lists" on the Entity, then
> (i.e. top level = set of indexes, second level = set of attributes
> in each compound index?)? Something sort of like Relationship
> editor might be appropriate maybe? Where you can create multiple
> indexes and in each one add a list of attributes to it ... I hadn't
> been thinking about MULTIPLE indexes, so I should rethink that
> boolean on EOAttribute.
>
> ms
>
> On Jul 19, 2006, at 7:52 AM, Pierre Frisch wrote:
>
>> Thanks but I need this info in the model. We also need to support
>> multi-column indexes. My preference would be for a dictionary with
>> the index name and the list of attributes.
>>
>> I am happy to help you with the SQL generation but to be honest
>> this is feature I never use. I do all my DB initialization using
>> EOF and code we have written over the years.
>>
>> Pierre
>>
>>
>> On 19-Jul-06, at 1:45 PM, Mike Schrag wrote:
>>
>>> Off-topic of the current discussion, I snuck an "isIndexed" field
>>> onto our EOAttribute :) Some wishful thinking ...
>>>
>>> ms
>>>
>>> On Jul 19, 2006, at 7:39 AM, Pierre Frisch wrote:
>>>
>>>> I particular I would like to support indexes, I have already the
>>>> code built in my application but the management in the EOModeler
>>>> user dictionary is far from optimal, so I was hoping that we
>>>> could do something as soon as the new modeler is operational.
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Jul 19 2006 - 17:59:43 EDT