On 8/20/20 9:21 AM, Shantanu Shekhar wrote:
Adrian,
The sequence is not set as a default on PK. The sequence is exclusively
being used by the ORM.
Then something there is generating negative numbers and using them to
populate the PK.
Thanks,
--
Adrian Klaver
adrian.kla...@aklaver.com
Adrian,
The sequence is not set as a default on PK. The sequence is exclusively being
used by the ORM.
Thanks,
Shantanu
On Wednesday, August 19, 2020, 06:28:53 PM EDT, Adrian Klaver
wrote:
On 8/19/20 3:24 PM, Shantanu Shekhar wrote:
Please reply to list also.
Ccing list.
> Thanks Adr
On 8/19/20 3:24 PM, Shantanu Shekhar wrote:
Please reply to list also.
Ccing list.
Thanks Adrian,
I will reach out to the ORM team and see if they can help me understand
this behavior.
I should have asked earlier, is this sequence set as a DEFAULT on the PK
field or is it just being used by
On 8/19/20 3:15 PM, Shantanu Shekhar wrote:
Team,
I have a sequence definition in Postgres 9.6.11 like so:
CREATE SEQUENCE IF NOT EXISTS org.my_seq
INCREMENT 1
MINVALUE 1
NO MAXVALUE
START 1
CACHE 20;
This sequence is used by a Java ORM framework to generate primary keys
for on
Team,
I have a sequence definition in Postgres 9.6.11 like so:
CREATE SEQUENCE IF NOT EXISTS org.my_seq INCREMENT 1 MINVALUE 1 NO MAXVALUE
START 1 CACHE 20;
This sequence is used by a Java ORM framework to generate primary keys for one
of our tables. The initial numbers generated by this seq
