Forum OpenACS Development: Response to a hack to the db_nextval hack

Collapse
Posted by Don Baccus on
Good end-all solution:
  • drop view "foo"
  • create sequence "foo" with the value of "nextval('t_foo')" (when there's only one user running!)
  • drop sequence t_foo
That's the gist of an upgrade SQL file.

Then find all references of "foo.nextval" and replace with "nextval('foo')" making sure they're in PG, not generic, query files

Repeat for every package in the system.

I think we need your hacked db_nextval for now but it would be nice if we could get folks who want to work on PG packages to take the time to remove the hack entirely on a package-by-package basis.