is ctrl + 0 to set a cell to NULL what you looking for?
Thank you, that's it!
Many many thanks! Had a few goofs lately and cursed my failing memory for having to take the long way around!
Originally Posted by shammat
What's wrong with using:
UPDATE theTabel SET theColumn = NULL;
(btw: $null is not a NULL value for the database)
$null, <null>, so many languages and platforms, "use what I mean, not what I say" and all that. Anyway, the UPDATE statement, besides being subject to disasterous where-clause error some late night, is many keystrokes distant vs. being right there in the EM GUI.
It's a quick "oops" fixer when in the GUI. If you type in the wrong column (ie: <null> is appropriate), then your alternative is either to let the update take place then go out and issue an UPDATE in another tool, exit the window prior to allowing the update to take hold (possibly loosing your recordset that my no longer be recoverable), or doing Ctrl/0.
So; this is not only much quicker, but has less risk of momentary bad data, or at least a quicker fix-up and return to <null>.
Actually; just this morning I was in there doing it. But thank you for your critisizm.
The value of doing Update and Create statements for everything is to apply to test environments first and for saving an audit trail.
My situation is a development environment where I'm tweaking the design on the fly. My brain just isn't able to visualize a perfect layout on paper, sorry. Also setting up and resetting test data easiest in a GUI.