flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Yang <flashflex...@gmail.com>
Subject Re: One to one relationship - best practices for Flex?
Date Thu, 11 Dec 2014 19:42:27 GMT
the database is for maintaining relationship(rmdb) and persistence, you
should have a layer to convert these entities into objects that responsible
for your UI.

On Thu, Dec 11, 2014 at 1:48 PM, Carlos Monteiro <uno.monteiro@gmail.com>
wrote:

> [off topic]
> google spam filter on it's best: "Girl" and "One to one relationship"
> equals spam!
>
> On 9 December 2014 at 18:43, 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.
> >
>

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