Image Upload / BLOB Storage - strange behaviour

[Tohawk]

Hi everybody,

I need to store images over a standard html form into a mysql-table MEDIUMBLOB-Field.

Getting the file works :

$file = mysql_real_escape_string(file_get_contents("php://input"));

At this point, I can just write $file into a new file:

 fwrite(fopen('dir', 'w'), $filet);

This works, so I conclude that uploading the file into a string works.

Now I want to put $file into the DB, therefore I use a simple INSERT-Statement, nothing special with that.

In a next step, I read (SELECT...) the $file out of the DB and write it to a file:

  $fh = fopen('dir/filename', "w");
                  fwrite($fh, ($file[data])); 
                  fclose($fh);

The problem: the written file is
a) ~ 4x as big as the input file (compression ?!)
b) not readable. ("Missing MetaTags if I try to open the image with gwenview).

What am I doing wrong? May mysql_real_escape_string trigger this behaviour?

Thanks for your advices, I'm stucked..
🙂

[dagon]

add the b flag to fopen

[Tohawk]

Hi dagon, thanks for your advice.

Unfortunately, the 'b'-flag doesn't solve the problem. But I think that it is really important:

http://php.net/manual/en/function.fopen.php wrote:

If you do not specify the 'b' flag when working with binary files, you may experience strange problems with your data, including broken image files and strange problems with \r\n characters.

The generated file is still ~ 4x as big as the input file.

The concerning table looks like that:

CREATE TABLE IF NOT EXISTS `filetbl` (
  `id` int(12) NOT NULL AUTO_INCREMENT,
  `data` mediumblob NOT NULL,
  `size` int(12) NOT NULL,
  `label` varchar(100) NOT NULL,

) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

Any other Idea?

[johanafm]

php://input is not available with enctype="multipart/form-data", which is what you should use for file upload.

Why not use $_FILES instead?