Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Insertable=false only being respected if updated=false also present

The default values I'm using are special to the DB vendor, so they
have to be set on the DB side. I think I'll file a bug, since it seems
like it should work either-or by my reading of the JPA spec.

Thanks for the reply.


On Wed, Aug 6, 2008 at 9:31 AM, James Sutherland <jamesssss@xxxxxxxxx> wrote:
> This is true, EclipseLink only has a read-only setting, which both setting
> map to.  If you do not wish to insert the field because you are defaulting
> in the database, you may wish to look into the ReturningPolicy or instead
> default the attribute value in Java.
> Feel free to log the bug though.
> Tim Hollosy wrote:
>> I need a sanity check. I've run into a problem recently on two
>> different entities where in my @Column annotation insertable=false is
>> ignored and the column included in an insert statement unless
>> updateable=false is also included in the annotation.
>> This is the first time I've tried insertable=false by itself. Am I
>> missing something here? I create my entity, call persist on it, then
>> commit. This seems a bit too major of a bug to still be around, so I'm
>> thinking I must have a misconception somewhere.
>> Perhaps I have some misconception about these attributes, could  but
>> they seemed pretty straight forward to me. Any ideas before I file a
>> bug report? (I'm on 1.0 osgi branch)
>> Thanks,
>> Tim
> -----
> ---
> James Sutherland
>  EclipseLink ,
> TopLink
> Wiki: EclipseLink ,
> TopLink
> Forums: TopLink ,
> EclipseLink
> Book: Java Persistence
> --
> View this message in context:
> Sent from the EclipseLink - Users mailing list archive at
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx

Back to the top