flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evyatar Ben Halevi-Arbib <evyata...@gmail.com>
Subject Re: One to one relationship - best practices for Flex?
Date Wed, 10 Dec 2014 09:31:00 GMT
You can create a designated data object that contains data coming from all


On Tue, Dec 9, 2014 at 8:43 PM, CodeGirl <MichelleNicholes@yahoo.com> wrote:

> I have a one to one relationship in my database.   In Java I would just
> extend one class.   But Databases are not Object related.   In JPA, on the
> web service, it wants to just make a field of the class type in the other
> class but this causes problems with the datagrid.   Especially around the
> dataField property.  It doesnt like field.field dataFields.   So, what is
> the best practice for my web service to return in a one to one relationship
> which I would like them both to merged together for my datagrid.
> --
> View this message in context:
> http://apache-flex-users.2333346.n4.nabble.com/One-to-one-relationship-best-practices-for-Flex-tp9044.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message