ereg_replace issue

November 9th, 2009, 9:24 am

hi there people

i have this code happening with regards to my wamp server. is this something that can be sorted out? would this happen on a normal remote server that has lamp on with the necessary bells and whistles?

Code: [ Download ] [ Select ]

Deprecated: Function ereg_replace() is deprecated in C:\wamp\www\itinwales\common\classes\class.paging.php on line 22

this is the code on line 22

Code: [ Download ] [ Select ]

$query = ereg_replace("^SELECT[[:space:]+]","SELECT SQL_CALC_FOUND_ROWS ",$query);

i have not come across coding like this before. is there a way that this can be written to work better or just to atually work?

cheers

November 10th, 2009, 3:40 am

hi there

i have tried using the code instead

Code: [ Download ] [ Select ]

$query = "SELECT ";
$query = preg_replace("/^SELECT +/i","$0 SQL_CALC_FOUND_ROWS ",$query);
echo $query;

1. $query = "SELECT ";
2. $query = preg_replace("/^SELECT +/i","$0 SQL_CALC_FOUND_ROWS ",$query);
3. echo $query;

but it brought up more errors.

i am using 5.0.4 on the remote server and 5.3.0 on my wamp server. what is the best php version to use? (5.2.11?)

hi there

also this "SQL_CALC_FOUND_ROWS" is this a command of some sort? i have not seen this before. i am trying to trawl thru another persons php shop. i downloaded the whole shop from one server and trying to put it up on another server. this is one of the 5 errors i am coming up against. anyone had any experience with this?

[Bigwebmaster]

November 11th, 2009, 2:42 pm

You can learn how to use the preg_replace function here:

http://php.net/manual/en/function.preg-replace.php

SQL_CALC_FOUND_ROWS is used with FOUND_ROWS() when you have a limit clause so that you can find out how many rows would have been returned if you didn't have the limit set. Here is a quick summary:

Quote:

A SELECT statement may include a LIMIT clause to restrict the number of rows the server returns to the client. In some cases, it is desirable to know how many rows the statement would have returned without the LIMIT, but without running the statement again. To obtain this row count, include a SQL_CALC_FOUND_ROWS option in the SELECT statement, and then invoke FOUND_ROWS() afterward

You can see some example usage here:

http://www.mysqlperformanceblog.com/200 ... ound_rows/

November 12th, 2009, 8:54 am

cheers for that BWM. bookmarked and ready to digest