Am 22.04.2019 um 20:35 schrieb Justin Pryzby:
Isn't it a best-practice to make a subclass of ProgrammingError just for that ? Else it encourages people to write "except ProgrammingError:" without also checking "if 'exactly one row' in e".
Good point. How shall we call it? Maybe "NoResultFound" and "MultipleResultsFound" like in SQLAlchemy? Or just "NoSingleRow" encapsulating both? -- Christoph _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo/pygresql
