r table.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Ferindo Middleton [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 14, 2006 9:16 PM
> To: Dan Buettner
> Cc: my
ble.
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -Original Message-
> From: Ferindo Middleton [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 14, 2006 9:16 PM
> To: Dan Buettner
> Cc
Good call on the WHERE email_address IS NULL thing. Also occurs to me
you could do a SELECT DISTINCT instead of just a SELECT to eliminate
duplicate update commands.
Glad this was useful.
Dan
On 10/14/06, Ferindo Middleton <[EMAIL PROTECTED]> wrote:
Thanks Dan. This does help. This a pretty
Thanks Dan. This does help. This a pretty straight-forward idea. I could
even save the results of this query to a text file and possibly review it a
little before running it so I don't acidentally do anything funky and I
could see the impact this would have on the data before applying it. I think
Ferindo, I had a similar task recently, and the problem you'll run
into is that you can't select from and update the same table at once.
What I ended up doing was doing a SELECT to build the update queries
for me.
Something like this:
SELECT CONCAT(
"UPDATE bowler_score SET email_address = '", em
I have a table, bowler_score_records, with the following columns: id,
firstname, middlename, lastname, race, religion, email_address,
bowling_score, gamedate
As records get entered to this table, sometimes the users forget to input
the email_address but the users always capture the full name, r
