Hi all,

Does anyone know why “branchcode” is nullable for the “reserves” table?

I’m occasionally finding I have reserves with a null branchcode, and it causes all kinds of problems.

Unfortunately, I can’t figure out how these reserves are being created, as the UI should be preventing this from happening. I’ve looked at the logs and tried to reproduce the problem myself and can’t do it. But the action_logs and the database itself confirms that there are reserves being created with null branchcodes at times.

If the database had branchcode as a NOT NULL column, we wouldn’t have this problem. So I’m curious why we haven’t done that… thoughts anyone?

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

Office: 02 9212 0899

Online: 02 8005 0595