List:General Discussion« Previous MessageNext Message »
From:Jerry Schwartz Date:June 9 2011 12:53pm
Subject:RE: Data missing after field optimization
View as plain text  
<snip>

>> If that's all you did, you indeed 'removed the default NULL' but did not
>specify another default. Hence, if you don't explicitly specify a value in 
>your
>insert statement, the insert can not happen as the server doesn't know what 
>to
>put there and is explicitly disallowed from leaving the value empty.
>
>	That makes sense.  So then why does phpMyAdmin allow you to choose "None"
>as a default?

[JS] There are times when you want to enforce certain conditions even though 
they might sometimes generate an error. Two examples are required fields (no 
default value) or referential integrity.

The goal is not to lose data, but to make sure your applications are doing 
what they are supposed to do. You would program your applications to trap and 
report errors.


Regards,

Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341
E-mail: jerry@stripped
Web site: www.the-infoshop.com






Thread
Data missing after field optimizationsono-io7 Jun
  • Re: Data missing after field optimizationJohan De Meersman7 Jun
    • Re: Data missing after field optimizationsono-io7 Jun
      • Re: Data missing after field optimizationRik Wasmus7 Jun
      • Re: Data missing after field optimizationJohan De Meersman8 Jun
        • Re: Data missing after field optimizationsono-io9 Jun
          • RE: Data missing after field optimizationJerry Schwartz9 Jun
        • Re: Data missing after field optimizationsono-io14 Jun
          • Re: Data missing after field optimizationJohan De Meersman14 Jun