Skip to content

fix for primary key result by replaced the SELECT next sequence value with RETURN - #30

Open
vidur wants to merge 1 commit into
MikeGriffinReborn:masterfrom
vidur:autoincrement_primarykey
Open

vidur wants to merge 1 commit into
MikeGriffinReborn:masterfrom
vidur:autoincrement_primarykey

Conversation

@vidur

@vidur vidur commented Feb 4, 2021

Copy link
Copy Markdown

This issue is happening with the AutoIncrement column. The problem was new record is getting saved to DB and the object doesn't have a primary key set after a successful transaction. I've made it so the object would set the DB's primary key set after the transaction complete.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant