What's wrong with this command?

[edhan]

Hi

I am trying to add additional field in wordpress table, but doesn't seem to work. Can anyone please tell me what's wrong with this command in my file called update.php.

Thanks!

<?
require('wp-config.php');
//DB_NAME
$notinstalled=false;
$db_wp_connection = mysql_pconnect(DB_HOST, DB_USER, DB_PASSWORD) or trigger_error(mysql_error(),E_USER_ERROR);

mysql_select_db($database_name, $db_wp_connection);

	$sql = "ALTER TABLE wp_posts ADD post_category INT (4) NOT NULL AFTER post_title";


?>

[kgun]

I am a little away from SQL now, but

have you tried the command from SQL command level?

Just wondering: Should it be

... ADD COLUMN ...

[edhan]

Originally Posted by kgun

I am a little away from SQL now, but

have you tried the command from SQL command level?

Just wondering: Should it be

... ADD COLUMN ...

post_category is the column I want to add after the post_title. I have done it in phpMyAdmin and it works. But I have alot of wordpress blogs to update so thinking of just writing a small php file where it will be easier to update them. I still can't figure out where I went wrong. arrrgghhhh ...

SOLVED:

Change the command to be like this:

<?
require('wp-config.php');
$db_wp_connection = mysql_pconnect(DB_HOST, DB_USER, DB_PASSWORD) or trigger_error(mysql_error(),E_USER_ERROR);

$database_name=DB_NAME;

mysql_select_db($database_name, $db_wp_connection);
$p_sql="select * from wp.posts";
$rs_table = mysql_query($p_sql, $db_wp_connection);
	$sq = "ALTER TABLE wp_posts ADD post_category INT (4) NOT NULL AFTER post_title";

mysql_query($sq) or die(mysql_error()." (script line: ".__LINE__.")");
?>

[Biggles]

I am not familiar with wordpress and am not sure if it is covered in your code somewhere else... but where is the $sql variable actually being sent to MySQL ?

maybe it's not the $sql but the call to the db thats failing?

[kgun]

Another question INT (4) or INT(4) ?

[edhan]

Thanks for your reply. I have solved it. You can see the code in previous reply.

I just copied it somewhere for one of the installations and this works!

[Steelchord]

Yep, it did strike me that the $database_name and $db_wp_connection variables weren't necessarily set with anything useful. I'm glad you got this one solved.