Re: EntityModeler fails to recognize localized attributes in fetch specifications
Re: EntityModeler fails to recognize localized attributes in fetch specifications
- Subject: Re: EntityModeler fails to recognize localized attributes in fetch specifications
- From: Mike Schrag <email@hidden>
- Date: Tue, 17 Nov 2009 14:16:37 -0500
Not currently ... Localized attributes are totally synthetic, added at runtime by Wonder. EM has no idea about them. Are you supposed to query against the _en form in the fetch spec? I would have thought you'd query against "name" and it would dynamically rewrite the attribute name at runtime based on the user's locale? I don't use these, though, so I don't know.
ms
On Nov 17, 2009, at 2:09 PM, Riccardo De Menna wrote:
> Hi,
>
> If I write a Fetch Specification in entity modeler that uses a qualifier with an attribute name that contains an underscore (for instance when using localized attributes) my generated templates end up containing errors.
>
> To be more clear... putting something like "visible = 1 and name_en = $name" in the qualifier field of the fetch specification.
>
> Result: Any entry like ${binding.attributePath.childClassName} in the template fails to be resolved.
>
> ${binding.attributePath} alone returns [EORelationshipPath: <invalid>]
>
> Is there a workaround? I'm stuck not being able to use fetch specifications if the argument is localized in the db.
>
> Riccardo De Menna _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden