Getting around MySql Error 1093 with a NOT IN Subquery?

Remove the SomeDB. Outertable from your query so it starts DELETE FROM SomeDB. Logging AS outertable.

Thanks, I've tried that one before. It results in Error Code: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AS outertable WHERE outertable. Log_id NOT IN ( SELECT SomeDB.f.

Log_id ' at line 2 – Tex Feb 24 at 16:34 Remove the AS clause, it is not part of the delete syntax. - dev.mysql. Com/doc/refman/5.0/en/delete.

Html – David Gillen Feb 24 at 16:45 This gets me back to Error 1093. Also, AS is a part of the DELETE syntax - check the docs more closely. It's covered under table_references in the JOIN syntax, which is referenced on the DELETE syntax page.

See: dev.mysql. Com/doc/refman/5.0/en/join. Html – Tex Feb 24 at 16:51 You're not joining on the DELETE you're joining on the sub SELECT.

What happens when you just run the sub query? – David Gillen Feb 24 at 17:32 AS is allowed in a DELETE query, whether or not I'm joining on it as per the reference to table_references in the linked doc you provided. AS works in the original example I provided - no syntax error is thrown, the query executes for around one minute, then dies with the 1039 error, completely different than a syntax problem.

The subquery alone works as expected - it returns exactly the records that I don't want to delete. – Tex Feb 24 at 18:03.

INNER JOIN SomeDB. Process_id = x. Log_id = x.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions