[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Mapping a Database View
|
No, that would give you identity/caching issues.
If there are 3 columns that will always make a row unique in your view
you can set that as a compound primary key for example.
./tch
On Fri, Sep 11, 2009 at 10:33 AM, RogerV <roger.varley@xxxxxxxxxxxxxx> wrote:
>
>
>
> tch wrote:
>>
>> Yeah that's the rub working with views, you'll either have to change
>> your view to have a unique id or make a multi-column @Id that's
>> reasonably unique across the view.
>>
>
> So, are you saying that I just "fake" a uniqueId by simply labelling it as
> such in my entity.java although there is no primary key defined in the
> database?
>
> Regards
>
> --
> View this message in context: http://www.nabble.com/Mapping-a-Database-View-tp25401383p25402082.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>
