Re: Default forced on MySQL; Basic SQL correctness should be higher priority than others

[Paul DuBois]

At 4:44 AM -0600 11/7/01, DownloadFAST.com wrote:
>My purpose in posting to this list was to see if any one else thought that
>basic SQL compliance is a priority.  Or if I am the lone person of my
>caliber in this community.  It is important for me to gauge what level of
>thinking is driving the development and use of MySQL.

"Of my caliber"?  Well, I don't know if anyone else shares your views
about SQL compliance, but you're certainly lone in being head and shoulders
in your arrogance about blasting in here on the mailing list and waving
your credentials around.  We've seen that kind of thing before, and it
shouldn't surprise you that reaction is so negative.


Anyway, the answer to your question may be to compile MySQL with the
DONT_USE_DEFAULT_FIELDS flag.  From the manual:

@cindex default values, suppression
@cindex suppression, default values
@item
You can configure MySQL not to use @code{DEFAULT} column values for
non-@code{NULL} columns (that is, columns that are not allowed to be
@code{NULL}).  This causes @code{INSERT} statements to generate an error
unless you explicitly specify values for all columns that require a
non-@code{NULL} value.  To suppress use of default values, run
@code{configure} like this:

@tindex CXXFLAGS environment variable
@tindex environment variable, CXXFLAGS
@example
shell> CXXFLAGS=-DDONT_USE_DEFAULT_FIELDS ./configure
@end example