Make it easier to debug an ElementCriteriaModel

[angrybrad]

Created by: Lindsey DiLoreto ([email protected]) on 2015/03/11 04:48:18 +0000
Votes at time of UserVoice import: 5

---

This is a very niche FR, but it would be extremely useful for complex plugin development.

PROBLEM:

How do you see what kind of SQL query your ECM is going to generate?

CURRENT SOLUTION:

$dbCommand = craft()->elements->buildElementsQuery($criteria);
$dbCommand->getText();

PROPOSED SOLUTION:

$criteria->getText();

("getText" is a mediocre term for that... it could be "debug", or "queryString", or whatever.)

---

When developing a plugin, anything that makes debugging easier is appreciated. It seems like it would be an easy win for the ECM to internalize a method for outputting the query string directly.

[angrybrad]

Posted by Michael ([email protected]) on 2015/03/11 15:06:07 +0000

---

Yeah, somehow I totally missed the part where you have a "CURRENT SOLUTION" listed out... in big capital letters... oops.

[angrybrad]

Posted by Lindsey DiLoreto ([email protected]) on 2015/03/11 04:48:18 +0000

---

@michael - Yup, that was actually noted in the original post (under "CURRENT SOLUTION").

But it would be awesome if getText were built directly into the ECM, so you wouldn't need that extra line of code just for debugging.

[angrybrad]

Posted by Michael ([email protected]) on 2015/03/11 15:06:07 +0000

---

@lindsey — You can do this debugging via the buildElementsQuery() method of the ElementsService. Post a question on SE and I'll be happy to elaborate.

[angrybrad]

Posted by Narration SD ([email protected]) on 2015/04/14 16:07:09 +0000

---

Yes, what Marion says, and a good idea all around -- makes much more transparency, for both old hands and those entering the Craft world...

[angrybrad]

Posted by Marion Newlevant ([email protected]) on 2015/03/10 22:04:02 +0000

---

Also probably need $criteria->getParams() to get the values it will bind