Any reason you're not using $wpdb->prefix for your table names?
–
mor7iferFeb 28 '12 at 13:04

Welcome to WPSE. Notes: wp_posts would $wpdb->posts... And you should really use prepare() and like_escape(). Examples can be found in pack of dozens all over the site. Also: Please show your whole class and how you call the class methods.
–
kaiser♦Feb 28 '12 at 13:52

@m0r7if3r - No reason, just keeping the code simple. Does that make any difference ?
–
LafanterFeb 28 '12 at 14:46

1

You've not included addKeyword_middle_bold_linked nor have you included the adjustments we've recommended.
–
Tom J Nowell♦Feb 28 '12 at 16:38

1

I would also recommend that you separate out the post update part into another function as you're re-implementing it in each function differently introducing inconsistency and potential errors
–
Tom J Nowell♦Feb 28 '12 at 16:40

Why you really should take care & stick 100% to the core when doing funny DB stuff

Portability - DB code can and should work everywhere. The wp_ prefix is only a default, which can get changed in the wp-config.php file by every beginner. Plus: It's recommended that you do so. Adding the prefix, will modify the query on the fly and let it proceed also in environments, where you have custom settings.

Further Readings…

This is a great post kaiser. I really appreciate your effort. But it dosnt solve any thing for me. I am going to post some more code that might give a real picture/understanding of the code.
–
LafanterFeb 28 '12 at 15:23