Probably glancing over this problem

[influx]

Hey all..this is driving me nuts, and I shouldn't be having a problem...at all.

I have the following code for when the users of my website want to delete all of the files uploaded in their user directory. I have a function to delete the contents of the directory (graciously provided by aidan as the rmdirr() function at: http://aidan.dotgeek.org/lib/?file=function.rmdirr.php) and that works fine..however when I try to update the rows in my MySQL database, it gives me the following error:

Duplicate entry '' for key 2

Here's the code:

if(rmdirr("user_upload/".$_SESSION['username']))
{
	$query = "UPDATE upload
	SET u_file1_name = '',
	u_file1_desc = '',
	u_file1_date = '00.00.0000',
	u_file2_name = '',
	u_file2_desc = '',
	u_file2_date = '00.00.0000',
	u_file3_name = '',
	u_file3_desc = '',
	u_file3_date = '00.00.0000',
	u_file4_name = '',
	u_file4_desc = '',
	u_file4_date = '00.00.0000',
	u_file5_name = '',
	u_file5_desc = '',
	u_file5_date = '00.00.0000'
	WHERE
	u_username='".$_SESSION["username"]."'";
	mysql_query($query) or die(mysql_error());
}
else
{
	echo 'We encountered an error trying to delete your files.';
	exit;
}

What the hell does this error exactly mean? If I am UPDATING the info in the database, what does it matter if there is a duplicate entry.

Thanks!
-influx

[xblue]

I'd take a look at all the name and description columns. You'd need to make sure that they allow duplicates (not marked as unique) if the code is supposed to be applied to more than one user (which it most probably is?)

Another option would be to create a separate table for this infomation that holds one file per record, and relate this to the user. This does not limit the number of files stored as your current design most probably does, and it allows you to completely delete these records.

[influx]

Here it is:

CREATE TABLE `upload` (
 `u_id` int(10) NOT NULL default '0',
 `u_username` varchar(40) default NULL,
 `u_file1_name` varchar(60) default NULL,
 `u_file1_desc` varchar(255) default NULL,
 `u_file1_date` varchar(10) default '00.00.0000',
 `u_file2_name` varchar(60) default NULL,
 `u_file2_desc` varchar(255) default NULL,
 `u_file2_date` varchar(10) default '00.00.0000',
 `u_file3_name` varchar(60) default NULL,
 `u_file3_desc` varchar(255) default NULL,
 `u_file3_date` varchar(10) default '00.00.0000',
 `u_file4_name` varchar(60) default NULL,
 `u_file4_desc` varchar(255) default NULL,
 `u_file4_date` varchar(10) default '00.00.0000',
 `u_file5_name` varchar(60) default NULL,
 `u_file5_desc` varchar(255) default NULL,
 `u_file5_date` varchar(10) default '00.00.0000',
 `u_file6_name` varchar(60) default NULL,
 `u_file6_desc` varchar(255) default NULL,
 `u_file6_date` varchar(10) default '00.00.0000',
 `u_file7_name` varchar(60) default NULL,
 `u_file7_desc` varchar(255) default NULL,
 `u_file7_date` varchar(10) default '00.00.0000',
 UNIQUE KEY `u_id` (`u_id`),
 UNIQUE KEY `u_file4_desc` (`u_file4_desc`)
) TYPE=MyISAM

u_id is there ID number assigned to them upon registering..

Obviously the problem lies in the fact that u_file4_desc is a UNIQUE KEY. Could you explain to me what exactly this means? How did this happen, it seems to be a mistake.

-influx

[xblue]

I think probably an index has been created on this column, maybe by accident.

Try removing the index:
ALTER TABLE tablename DROP INDEX indexname