On Mon, 26 Aug 2019 at 01:42, Tom Lane wrote:
> Vik Fearing writes:
> > On 25/08/2019 18:59, Tom Lane wrote:
> >> Vik Fearing writes:
> >>> Is there a reason why the serial pseudotypes still behave as they did
> >>> pre-v10 and don't map to G
On 25/08/2019 19:42, Tom Lane wrote:
> Vik Fearing writes:
>> On 25/08/2019 18:59, Tom Lane wrote:
>>> Vik Fearing writes:
>>>> Is there a reason why the serial pseudotypes still behave as they did
>>>> pre-v10 and don't map to GENERATED BY DEF
Vik Fearing writes:
> On 25/08/2019 18:59, Tom Lane wrote:
>> Vik Fearing writes:
>>> Is there a reason why the serial pseudotypes still behave as they did
>>> pre-v10 and don't map to GENERATED BY DEFAULT AS IDENTITY these days?
>> Backwards compatibi
On 25/08/2019 18:59, Tom Lane wrote:
> Vik Fearing writes:
>> Is there a reason why the serial pseudotypes still behave as they did
>> pre-v10 and don't map to GENERATED BY DEFAULT AS IDENTITY these days?
> Backwards compatibility?
With what? We don't support downgrading and
Vik Fearing writes:
> Is there a reason why the serial pseudotypes still behave as they did
> pre-v10 and don't map to GENERATED BY DEFAULT AS IDENTITY these days?
Backwards compatibility?
regards, tom lane
Is there a reason why the serial pseudotypes still behave as they did
pre-v10 and don't map to GENERATED BY DEFAULT AS IDENTITY these days?
I'm hoping it's just an oversight and I can help "fix" it, but maybe
there is an actual reason for it to be this way?
--
Vik Fearing
