Re: temp table or query for API
Posted by: Rick James
Date: May 31, 2013 09:44PM

1. The prefix "field_data_field_" clutters the query, can you remove it?

2. The database seems to be over-normalized. Was some program trying to do that for you?

3. Is your question about performance? If so, "100's of times an hour" is a yawner; "100's of times a _second_" becomes interesting.

4. "Would it be faster or better to setup a temp table or stored procedure" -- probably not. Less normalization would probably help more.

5. This combination does not make sense:
LEFT JOIN media_type
WHERE media_type.media_type ="video"
LEFT JOIN allows the righthand table to be missing a row, and it delivers NULLs to the rest of the query. In this case you are insisting on a non-NULL value (media_type ="video").

6. I see this again and again: "on field_data_field_xx.revision_id=node.vid"; what the heck is going on?

Is this some 3rd party software? What is it's name? I want to announce to the world what a piece of xxxx it is!

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.