Reserve room for system config.metabib_field values
Bug #1097399 reported by
Dan Scott
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
2.3 |
Fix Released
|
Medium
|
Unassigned | ||
2.4 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
* Evergreen 2.3 and prior
Per http://
So, something like changing Open-ILS/
SELECT SETVAL(
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → 2.4.0-alpha |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
milestone: | 2.4.0-beta → 2.4.0-rc |
Changed in evergreen: | |
milestone: | 2.4.0-rc → none |
no longer affects: | evergreen/2.2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
For that matter, the same problem applies to:
SELECT SETVAL( 'permission. grp_tree_ id_seq' ::TEXT, (SELECT MAX(id) FROM permission. grp_tree) );
SELECT SETVAL( 'permission. grp_penalty_ threshold_ id_seq' ::TEXT, (SELECT MAX(id) FROM permission. grp_penalty_ threshold) );
SELECT SETVAL( 'permission. grp_perm_ map_id_ seq'::TEXT, (SELECT MAX(id) FROM permission. grp_perm_ map));
Maybe we want to make the value 1000 instead of 100? Integers are cheap...