I get the following messages when trying to delete a picture through coppermine
"While executing query "DELETE FROM cpg11d_exif WHERE filename='albums/test/139.jpg' LIMIT 1" on 0
mySQL error: Table 'fredda_se.cpg11d_exif' doesn't exist"
I've ran the update.php file again and it says,
"CREATE TABLE cpg11d_exif ( `filename` text NOT NULL default '', `exifData` text NOT NULL, UNIQUE KEY `filename` (`filename`) ) TYPE=MyISAM Already Done "
But hell no, it's not done. It doesnt exist in my database.
When turning on "Read EXIF data in JPEG files" I can't even view my pictures!
Solution?
//F
What does this have to do with the 1.4 beta?
I didn't have the problem on my previous version 1.2.1.
It has occured since the update...
But if you so wish, then move it to some sort of official support page?
//F
You upgraded to the beta version, 1.4.1?
Yes I did.
Does your db user have the CREATE privilege ?
I don't know if this will help, but I had something similar happen to me. Using Admin Tools and
rebuilding the thumbnails and intermediate pictures in the suspect album sorted out the problem for me.
Dennis
There is no suspect album. Can't delete any picture in any album without alot of huzzle.
Tried to rebuild all the thumbs but that didn't help.
The DB user must have CREATE privilege, otherwise I shouldn't been able to install the script from the begining?
More suggestions please! This must be fixed!
//F
your webhost might have changed permissions, so the initial install will have succeeded (while the db user had the create privilege), but when upgrading, the privileges might have been different then. Try this for yourself - use a tool like phpMyAdmin and run this query: CREATE TABLE cpg11d_exif ( `filename` text NOT NULL default '', `exifData` text NOT NULL, UNIQUE KEY `filename` (`filename`) ) TYPE=MyISAM
If it fails, contact your webhost. Post feedback here.
This does need looking at though, we can't assume 'already done' just because the query fails.
if (@mysql_query($q)) {
echo "<td class='updatesOK'>OK</td>";
} else {
echo "<td class='updatesFail'>Already Done</td>";
}
Quote from: GauGau on September 29, 2005, 08:30:03 AM
your webhost might have changed permissions, so the initial install will have succeeded (while the db user had the create privilege), but when upgrading, the privileges might have been different then. Try this for yourself - use a tool like phpMyAdmin and run this query: CREATE TABLE cpg11d_exif ( `filename` text NOT NULL default '', `exifData` text NOT NULL, UNIQUE KEY `filename` (`filename`) ) TYPE=MyISAM
If it fails, contact your webhost. Post feedback here.
Okey, sorry for the slow feedback here. It's been other things on the "to do list".
I've tried the proposed suggestion, with the following result:
SQL-fråga :
CREATE TABLE cpg11d_exif(
`filename` text NOT NULL default '',
`exifData` text NOT NULL ,
UNIQUE KEY `filename` ( `filename` )
) TYPE = MYISAM
MySQL sa:
#1170 - BLOB column 'filename' used in key specification without a key length
There is no doubt that the user has create privileges. There's something else that's just not playing out right.
Ah, that query is indeed wrong - it should be this
CREATE TABLE CPG_exif (
`filename` varchar(255) NOT NULL default '',
`exifData` text NOT NULL,
UNIQUE KEY `filename` (`filename`)
) TYPE=MyISAM;