No, there is no need for the default value in the code or in the SQL definition.  I just erred in the field definition.  This patch should fix the problem.

 

Sorry for the bug,

Bob