@kaiser that's pretty inevitable when dealing with complex queries... btw there so should be post field (as in MySQL field, not custom) query in same manner as meta query
Want to move beyond the basics of WordPress? Simply go watch everything on http://wordpress.tv/. Beware, it's addicting.
@Rarst Just went through all that stuff, build a couple of different solutions... and finally just used the 's' arg to get a LIKE statement for post_title. Sometimes things seem so complicated, when they're sooo easy :)
@Rarst To sum it up: There's simply no need for any other thing aside from the s arg, as it wouldn't make any sense to use a LIKE on a status, date or ID.
I'm Jin, I work on the designs for the Stack Exchange sites as they graduate from the beta phase. Each site will have its own unique theme that will reflect its topic and culture. However, all sites will share common elements so they feel like they're part of the Stack Exchange family.
For our T...
Hi all. I'm Jin, and I'll be working on the designs for the Stack Exchange sites as they graduate from the beta phase. Each site will have its own unique theme that will reflect its topic. However, all sites will share quite a bit of common elements so they feel like they're part of the Stack Exc...
getting strange results from MySQL … this is so annoying.
SELECT SQL_CALC_FOUND_ROWS mu_4_posts.ID
FROM mu_4_posts
WHERE 1=1
AND (((mu_4_posts.post_title LIKE '%furc%')
OR (mu_4_posts.post_content LIKE '%furc%')))
AND mu_4_posts.post_type IN ('post', 'page', 'attachment')
AND (mu_4_posts.post_status = 'publish')
ORDER BY mu_4_posts.post_date DESC
LIMIT 0, 4
Some results do not contain the search string. I don’t understand it. :/
there is some code in $wpdb that sets up conenction, maybe something goes bonkers there... is there a way to pull opened connection properties? don't know
It's because of the collation you are using.
Anything that ends with _ci is case-insensitive (and also accent/umlaut insensitive). So yes, MySQL will consider "günni" and "gunni" the same thing, unless you change your collation.
Docs: http://dev.mysql.com/doc/refman/5.0/en/charset-table.html
@Mamaduka your code should run wherever it finds itself, so well written code that makes few assumptions and behaves cautiously checking for failures etc and testing for minimum versions should run well
@Rarst or both. In the best case scenario code should do well, but it's always good to fail gracefully. For example, in the Auditor I only support v3.3 and above, rather than crashing out I check for the WP version and nudge the user to update WordPress if it fails
For the sake of all us, who love zombie movies:
Please add a »28 hours later…« feature.
Wouldn't that look much nicer, than »1 day later« ?
I even added some blood in MS Paint to illustrate this.
SELECT * FROM table WHERE some_field LIKE ('%ö%' COLLATE utf8_bin)
For the sake of all us, who love zombie movies:
Please add a »28 hours later…« feature.
Wouldn't that look much nicer, than »1 day later« ?
I even added some blood in MS Paint to illustrate this.
