>>>>Hi,
>>>>
>>>>I am wondering (want to make sure I won't regret at some point) if setting default to many columns is ok (from the stand-point of good db design practice). For example, I have a table that has 34 columns and it looks like I will have defaults set for 30 columns (some 0, some empty string ''). Is this ok? TIA.
>>>
>>>In our tables practicatelly all fields have defaults except date fields. The regretful part of it is that we've been using deprecated (not yet) bound types for constants.
>>
>>First, thank you for making me feel better (about too many defaults). But what do you mean by "deprecated" types?
>
>There are two ways to make a default. We were bounding defaults to a type and that syntax is deprecated.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham