I think we would need to put this inside the userInfo dictionary ...
Pierre made a good point where he was mentioning that they need
access to that data at runtime. If we add totally custom entries in
the plist files (like in my original index flag, too), there is no
API on EOModel/Entity/etc to get access to that data. Your design
remains totally valid, though -- just that it would be key name
"Indexes", value = the dictionary you defined.
ms
On Jul 19, 2006, at 9:03 AM, Watkins, Garry wrote:
> I think that you should leave the field in attribute (for simple
> indices) and add another tab for the Entity Property editor to
> allow index definition. Also need to allow for unique and
> clustered index options. So I am thinking that it is a dictionary
> that looks like this in the <ENTITY>.plist
>
> Indexes = {
> byName = {columns = (a,b,c); comments=”blah blah blah”; clustered =
> “true”; unique = “false” userInfo = { <a userinfo dictionary>};}
> byXYZ = {columns = (x,y,z); comments=”blah blah blah2”; clustered =
> “false”; unique = “false” userInfo = { <a userinfo dictionary>};}}
>
> Thanks again.
> Garry
>
>
> On 7/19/06 8:00 AM, "Mike Schrag" <mschra..dimension.com> 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.
>>>>>
>>>>
>>>
>>
>>
>
>
> --
> Garry Watkins
>
> Database Administrator
> Motley Rice LLC
> 843-216-9639
>
>
> Confidential & Privileged
> Unless otherwise indicated or obvious from its nature, the
> information contained in this communication is attorney-client
> privileged and confidential information/work product. This
> communication is intended for the use of the individual or entity
> named above. If the reader of this communication is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error or
> are not sure whether it is privileged, please immediately notify us
> by return e-mail and destroy any copies--electronic, paper or
> otherwise--which you may have of this communication.
This archive was generated by hypermail 2.0.0 : Wed Jul 19 2006 - 09:12:49 EDT