I found a bug in the in-line search. I have a custom query for the table inner joining two tables, both have a column named "name". When the in-line search attempts to build the query, it errors because of an ambiguous column name. Has anyone run across this before?
I found the line of code that causes the error. It looks like the $field variable is just the column name and not the table + column. I don't know if there is a way to pass the table and then concat the two??
$qwery .= "LOWER($field)".$qopers[$op]." LOWER(".$v.")";
Also, I found that if you use the select_command and use the select * from (MY STATEMENT) as o, this breaks the in-line search. It doesn't have the proper format for sql. I had to go through and take those out.
All you need is to use following with column definition. This will resolve the name conflict for searching.
Ok, so that would require me to setup the columns manually and not use the auto-populate option, like I am currently using. I will give it a try.
The design of the midsole is relatively common, the drop between the front and rear palms is not too big, and the color of the midfoot and heel position is distinguished. The overall thickness is OK. The midsole uses a new technology, Formula 23 foam, which is in AJ37 and Luka 1st generation are also used, it is estimated that Jordan’s new models will have his presence.
We are sorry that this post was not useful for you!
Let us improve this post!
Tell us how we can improve this post?