Ticket #20 (closed defect: fixed)
Column re-definition with kargs inconsistent in autoload scenario
|Reported by:||guest||Owned by:|
Since r221, it's been disallowed to override columns in autoloaded tables. However, it appears that in the case where a keyword argument is passed to the field definition, the duplicity is not checked, and the expected exception is not thrown.
Originally, I thought it was the key="attribute_name" parameter that was avoiding the exception, but it also appears even primary_key=True will avoid the exception.
A complete example written as a unit test is included with this ticket. In this example, the Person class initializes correctly (when it shouldn't), but the Animal class throws the expected exception.