Issue #3483: use nextval() instead of SQL - koji

koji

#3483 use nextval() instead of SQL

Closed: Fixed 2 years ago by tkopecek. Opened 2 years ago by tkopecek.

We've nextval() helper but in many places is still direct SQL used. Let's replace it.

jcupova commented 2 years ago

PR 3484

Metadata Update from @jcupova:
- Custom field Size adjusted to None

2 years ago

tkopecek commented 2 years ago

Commit 93ca7ff fixes this issue

tkopecek commented 2 years ago

Commit 3fc402d fixes this issue

Metadata Update from @tkopecek:
- Issue set to the milestone: 1.30.1 (was: 1.31)
- Issue status updated to: Open (was: Closed)
- Issue tagged with: no_qe

2 years ago

Metadata Update from @tkopecek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

Normal

Milestone

1.30.1

Size

None

Related Pull Requests

#3484 Merged 2 years ago

koji

Source Code

Documentation

#3483 use nextval() instead of SQL Closed: Fixed 2 years ago by tkopecek. Opened 2 years ago by tkopecek.

Metadata

tech-debt no_qe

Related Pull Requests

#3483 use nextval() instead of SQL

Closed: Fixed 2 years ago by tkopecek. Opened 2 years ago by tkopecek.