Re: Performance/handling limit on mysqli_real_escape_string() function?

"Jacob Kruger" <[email protected]>
Newsgroups gmane.comp.php.windows
Message-ID <4F08E8518D4D40BB9EF6F66CF935FE2E@JacobPC>
Thanks - looks pretty much exactly what I want to try achieve, so will try 
modd'ing my code/script and see if works...<smile>

Also nice to maybe use the actual parameter binding for a change instead of 
just building up sql statement strings using sprintf() etc. - know better 
practice anyway.

Stay well

Jacob Kruger
Blind Biker
Skype: BlindZA
'...fate had broken his body, but not his spirit...'

----- Original Message ----- 
From: "Pierre Joye" <[email protected]>
To: "Jacob Kruger" <[email protected]>
Cc: "php-windows" <[email protected]>
Sent: Tuesday, August 13, 2013 9:08 AM
Subject: Re: [PHP-WIN] Performance/handling limit on 
mysqli_real_escape_string() function?


hi!

On Mon, Aug 12, 2013 at 11:24 PM, Jacob Kruger <[email protected]> wrote:
> What with trying to store image data in mySQL database, I am saving the 
> results of fread() function carried out using the file handle returned 
> from fopen(), with the "rb" argument to tell it the file is for binary 
> reading.
>
> Either way, for example, this specific image file is a 2.1Mb PNG file, and 
> mySQL server on my local, windows development machine seems to lock up 
> roundabout when I tell it to carry out the mysqli_real_escape_string() 
> function on the value of the variable that now contains the data read from 
> the physically uploaded file, and just wondering if this could be 
> something like a process overload, etc., and whether should just try 
> taking out the string real escaping for now, or whether that's likely to 
> cause problems, or should I try something like splitting the file's data 
> into more manageable size chunks, carry out the string escaping on those 
> chunks one at a time, with even a possible form of pause inbetween, and 
> then re-append them together before writing them to the database, or 
> should I maybe just implement at least a form of file size limit, which 
> might be an issue if the user will insist on certain image sizes, 
> resolutions, etc. etc.?
>
> Thoughts/suggestions?

Not really windows specific, php-database could fit better for this
question but here is what you should do:

https://blogs.oracle.com/oswald/entry/php_s_mysqli_extension_storing

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org


-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.