>Adrian Klaver wrote: >> Kevin Brannen wrote: >> It goes on to say a trigger is the right way to do this. So yeah, a >> "tightening of the code" seems to be hitting me because of bad code from the past. >> >> Problem identified and I'll solve it tomorrow. > >Glad it was solved. > >However, looking a gift horse in the mouth, did this not error when moving from the 9.6.5 instance to the first 12.2 instance? > >Or > >Was the constraint added in the first 12.2 instance? This is the first instance. :) I've now got our entire code base working on the latest version of Perl and Postgresql (they have to go at the same time because of DBI/DBD) and I'm going thru and making sure everything works before committing to our integration branch for further testing. I've solved a few other upgrade issues like some names changing in pg_catalog and moving to the community RPMs instead of compiling our own. The problem in this thread has been the only hard one and fortunately for me it's the last (or I think it is). Unless we have a significant reason, upgrading is hard enough we only upgrade about every other year, or that's my plan going forward. Waiting 3 years like we did this time makes for a larger jump than I'd like. Thanks again for the help! Kevin . This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, distribution, review, copy or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify us by reply e-mail, and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.
