You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@openjpa.apache.org by Laird Nelson <lj...@gmail.com> on 2010/02/12 21:48:49 UTC

Should DBDictionary instances call Column#setAutoAssigned(true)?

I've noticed that none of the DBDictionary instances that ship with OpenJPA
call Column#setAutoAssigned(true), even when it is within their power to do
so.

Is this by design?  Does this decision logically lie elsewhere?

Thanks,
Laird

Re: Should DBDictionary instances call Column#setAutoAssigned(true)?

Posted by Miłosz Tylenda <mt...@o2.pl>.

Hi Laird,

What exactly would you like to achieve by calling Column#setAutoAssigned(true)? Do you want for some databases the default GenerationType be IDENTITY? If this is the question, I suspect the TABLE type has been chosen as a default as it is the most portable across databases.

Cheers,
Milosz

> I've noticed that none of the DBDictionary instances that ship with OpenJPA
> call Column#setAutoAssigned(true), even when it is within their power to do
> so.
> 
> Is this by design?  Does this decision logically lie elsewhere?
> 
> Thanks,
> Laird
>