Actually we are going to get rid of DerivedDbAttribute past 1.2.
Right now you may try to change the DbAttribute "name" property with
the full column definition (haven't tried that myself - not sure
whether this works or not), but in the next major release it looks
like we need to add a "definition" property to DbAttribute.
Andrus
On May 14, 2006, at 5:22 PM, Watkins, Garry wrote:
> How does Cayenne support derived columns (from an EOModel) in a
> DbEntity? I
> am working on the import of an EOModel derived column formula, and it
> appears that my import is good.
>
> However, it looks like Cayenne Modeler does not support a
> DerivedDbAttribute
> in a regular DbEntity? Is that true? Does the framework support that
> combination? If that is true, then I won't worry about the modeler
> GUI not
> showing it correctly.
>
> This is what I have from the EOModel plist for the attribute:
>
> attributes = (
> {
> allowsNull = Y;
> definition = "dbo.years_diff(tsDateOfBirth, tsDateOfDeath,
> GETDATE())";
> name = age;
> valueClassName = NSNumber;
> valueType = l;
> }, ...)
>
> I create a DbDerivedAttribute called AGE, with the definition is
> the spec.
>
> Thanks
> Garry
>
>
> On 5/14/06 1:45 PM, "Watkins, Garry" <gwatkin..otleyrice.com> wrote:
>
>> Thanks Andrus,
>>
>> I am going to try and help you guys out again. It has been over a
>> year
>> since I contributed anything. Any way, I am currently working on the
>> EOModel import routine. I found some issues with it, and I just
>> about have
>> a patch to fix those items. I will open up a Jira issue once I
>> get done.
>>
>> I really am interested in making EOModels work instead of
>> Cayenne.xml,
>> because I want to use WOBuilder and have the key completion work with
>> EOGenericRecords. I will be building a WOCompatibility framework
>> to address
>> those needs. So if anyone has any ideas about what I should add
>> please let
>> me know.
>>
>> Thanks
>> Garry
>>
>> On 5/12/06 6:00 PM, "Andrus Adamchik" <andru..bjectstyle.org> wrote:
>>
>>>
>>> On May 12, 2006, at 2:39 PM, Mike Kienenberger wrote:
>>>
>>>> On 5/12/06, Watkins, Garry <gwatkin..otleyrice.com> wrote:
>>>>> I am using NestedECs a bunch, is Cayenne's nested dataContext
>>>>> working
>>>>> yet?
>>>>
>>>> I think so, but Andrus would know for sure.
>>>
>>> Yep, nested DataContexts are fully supported.
>>>
>>>
>>>>> Does Cayenne have an EOGenericRecord equivalent yet?
>>>>
>>>> Yes, but I don't know if it's been seriously tested yet.
>>>
>>> Still it should work ok, as a generic record in Cayenne is just a
>>> CayenneDataObject, same as used as a common superclass already.
>>>
>>>
>>>>> Can I just use a .eomodeld instead of a cayenne.xml?
>>>>
>>>> No, but the modeler can read it in and save it back out as
>>>> cayenne.xml.
>>>
>>> Theoretically you can customize the runtime to load an EOModel
>>> directly ... although there may be some issues converting
>>> inheritance
>>> and fetch specs, so you' probably want to import the EOModel in the
>>> Modeler, fix anything that doesn't look right, and then save as a
>>> Cayenne project.
>>>
>>> Andrus
>>>
>
> --
> 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 : Tue May 16 2006 - 16:18:27 EDT