On Mon, Jul 15, 2013 at 03:44:42PM +0100, Graeme Geldenhuys wrote: > On 2013-07-15 15:06, Henry Vermaak wrote: > > Could you explain why the above is bad for those of us that aren't DB > > experts? To my untrained eye it looks fairly plausible, so I'm > > obviously missing something. > > I never inserted data into column C, so MySQL decided on its own that it > should magically contain the value 0 — inventing data! Last time I > checked 0 <> null in SQL terms either.
I seem to remember something about table columns having default values in the definition, so perhaps column C defaults to 0? 0 != NULL, so it didn't break your definition? Henry -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
