On 4/6/17 23:13, David Rowley wrote:
> On 7 April 2017 at 00:44, Peter Eisentraut wrote:
>> Identity columns
>>
>> This is the SQL standard-conforming variant of PostgreSQL's serial
>> columns. It fixes a few usability issues that serial columns have:
>>
>> - CREATE TABLE / LIKE copies default bu
On 7 April 2017 at 00:44, Peter Eisentraut wrote:
> Identity columns
>
> This is the SQL standard-conforming variant of PostgreSQL's serial
> columns. It fixes a few usability issues that serial columns have:
>
> - CREATE TABLE / LIKE copies default but refers to same sequence
> - cannot add/drop
On 4/6/17 10:24, Tom Lane wrote:
> This commit is causing a compiler warning for me:
>
> tablecmds.c: In function 'ATExecSetIdentity':
> tablecmds.c:5936: warning: 'address.objectSubId' may be used uninitialized in
> this function
> tablecmds.c:5936: warning: 'address.objectId' may be used uninit
Peter Eisentraut writes:
> Identity columns
This commit is causing a compiler warning for me:
tablecmds.c: In function 'ATExecSetIdentity':
tablecmds.c:5936: warning: 'address.objectSubId' may be used uninitialized in
this function
tablecmds.c:5936: warning: 'address.objectId' may be used unini
Identity columns
This is the SQL standard-conforming variant of PostgreSQL's serial
columns. It fixes a few usability issues that serial columns have:
- CREATE TABLE / LIKE copies default but refers to same sequence
- cannot add/drop serialness with ALTER TABLE
- dropping default does not drop s