Re: [eclipselink-users] Custom SQL for relationship

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] Custom SQL for relationship

From: cinhtau <cinhtau@xxxxxxxxx>
Date: Sat, 27 Nov 2010 05:35:22 -0800 (PST)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

Can you post your Entity definition (source)? In my understanding:

Company and Employee @ManyToMany-Relationship = yes/no?
Usually you define a JoinTable, if it is @ManyToMany
Why don't you store the default Company with @OneToOne as extra attribute, besides design issues?

Bálint Kriván wrote:

I have to entites: Employee, Company. An Employee can be employed in many Companies, but there is a special Company which should be interpreted as the default one

View this message in context: Re: Custom SQL for relationship
Sent from the EclipseLink - Users mailing list archive at Nabble.com.

Follow-Ups:
- Re: [eclipselink-users] Custom SQL for relationship
  - From: Bálint Kriván

References:
- [eclipselink-users] Custom SQL for relationship
  - From: Bálint Kriván

Prev by Date: Re: [eclipselink-users] Custom SQL for relationship
Next by Date: Re: [eclipselink-users] Custom SQL for relationship
Previous by thread: Re: [eclipselink-users] Custom SQL for relationship
Next by thread: Re: [eclipselink-users] Custom SQL for relationship
Index(es):
- Date
- Thread

Breadcrumbs