acq.purchase_order 'state' field should have a check constraint

[Ben Ostrowsky]

It's possible to UPDATE acq.purchase_order SET state = 'Massachusetts' without the database complaining. In order to prevent this, the 'state' field should be defined as TEXT NOT NULL DEFAULT 'new'::TEXT CHECK (state IN ('new','pending','on-order','received','cancelled'))

[Bill Erickson (berick)]

Branch for master/2.2

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp893193-acq-po-state-constraint

[Bill Erickson (berick)]

Branch for 2.1 and 2.0. For 2.0, be sure to only cherry-pick the tip and not merge the entire branch.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp893193-acq-po-state-constraint-2_0-and-2_1

[Michael Peters (mrpeters)]

Tested /user/berick/lp893193-acq-po-state-constraint against master and it did the job.

Don't have a 2.1 test system right now, but I can't imagine any reason it wouldn't work the same there.

user/mrpeters-isl/lp893193-acq-po-state-constraint_signoff
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=c3be6b1601cd3da23ffbc040eee89a7674b40a2d

[Lebbeous Fogle-Weekley (lebbeous)]

Merged to master, rel_2_2 and rel_2_1 (rel_2_0 being dead).

Thanks Ben, Bill, and Mike!