I suspect that the field with the default value was a foreign key in another table (which is, I'll admit, another way of saying there was a defined relationship). One should not have default values for FK's as there is often no match. If you had a value of 0 in the related field of the other table, you probably would not have noticed - until you started getting weird query results if it was the many side, or error messages about unique values violation if it was a one to one relationship. Also, the order in which you choose the parent/child table can cause this issue - it may be backwards.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.