fenway

It'll annoy people, and then alot of people won't bother using the service if they can't get any help? If people expect ANYTHING in terms of reliability from a FREE service, they're fooling themselves. It's an illusion. Gmail can turn off tomorrow, delete all of your e-mail, not tell you, and it's your fault, not theirs. Well if Gmail did close tomorrow they would be up for a lot of legal costs as part of the gmail contract is that they will provide 99.5% uptime and if they break that contract a lot of people would sue google. As it is people almost sued google when did went down for a few hours but google argued because it only effected 25% of the customers therefore they could be down 4 times the time mentioned on the contract. Lucky <blank> See Mchl's post -- Google owes nothing to anyone.

It'll annoy people, and then alot of people won't bother using the service if they can't get any help? If people expect ANYTHING in terms of reliability from a FREE service, they're fooling themselves. It's an illusion. Gmail can turn off tomorrow, delete all of your e-mail, not tell you, and it's your fault, not theirs.

Or what? It's a free service.

Not sure what you're trying to do... multi-valued insert statement?

Don't store comma-separate values.

Why are you single quoting everything????

Yeah, it's the whole 1970 vs epoch thing.

MySQL won't combine individual column indexes for FULLTEXT -- use the combined one.

Huh?

mysql_select_d()?

Bad idea - just have a single rss table.

Check mysql_error() after the offending query.

Sorry, we (myself & mysql) don't believe it. LEFT JOIN and I'll bet you'll see NULLs.

I think you can simply using RENAME DATABASE as of version 5.something -- check the refman.

That's because you're likely running in strict mode -- if you say something has to be a string, and you don't insert anything, and the default isn't a string, then that's considered data corruption.

You're missing AUTO_INCREMENT.

That's quite enough.

Like I said... echo the full query.

Well, since you're named the index the same, you need to drop the other one first -- or give it a different name.

Don't double-post -- first & last warning.

If you're talking about auditing, you'll need to have the DB wrapper log this somehow (triggers, inserts, meta data, query logs, etc.) and then report it yourself.

Then there are no matches in the non-leading tables.

What does that even do? OP: you're talking about paging nwo?

Echo the ACTUAL query you're sending to the server -- and you'll see.

Then update a "modified" field, and check that afterwards.