[thesite] Fw: Someone is talking...

[Warden, Matt]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> From: "rudy" <r937 at interlog.com>
> Subject: Re: [thesite] Fw: Someone is talking...
> 

> i know if i touch these queries then something in the code around
> them is bound to break...  sorry to be a such wuss, but it's an old
> rule of thumb in programming -- you weight the benefit of fixing
> something against the inevitable pain of breaking something
> unrelated

You'd lose the ability to change the wording for the author's email
as well.

> so authors who also comment on their own articles are just gonna
> have to keep putting up with getting two "someone is talking"
> emails...

Ok, I haven't seen this code and I'll root through all the files and
eventually find it. But, I'm assuming that the replies and user
tables are already joined in the query (I'd think they'd have to be).

If we wanna avoid this double-email (which, as I've realized from my
latest article, is really quite annoying, I must say), could we not
simply join content as well and add a where clause to the "replies"
query (as opposed to the author query) the effect of " and not
content.userid=user.userid"?

Just throwing that out there. I dont really know how much of a
performance hit that entails and a big part of me assumes that if
this was a good idea, the SQLGod(tm) would have mentioned it.

So, this is just in case. Word on the street is he had quite a few
beers last night.

- --
mattwarden
mattwarden.com

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>

iQA+AwUBOxbpV3gH0dUmEhrcEQISVQCYlV6YVthCe6swTIoQmlV4A1RxAACgyY97
30Z+oO5Crp0i8RvFXEYau2E=
=YdF5
-----END PGP SIGNATURE-----