Neeraj Agarwal a écrit :
On Sun, Mar 28, 2010 at 12:59 AM, Marc Delisle marc@infomarc.info wrote:
Neeraj Agarwal a écrit :
On Sun, Mar 28, 2010 at 12:38 AM, Marc Delisle marc@infomarc.info
wrote:
Neeraj Agarwal a écrit :
On Sat, Mar 27, 2010 at 11:41 PM, Marc Delisle marc@infomarc.info
wrote:
Neeraj Agarwal a écrit : > Hi, > > We should have both the current status and historic data upto a user defined How do you plan to collect this historic data?
Hi
We can create triggers for each query which can make up our database.
Or can create a library which the user can add to their scripts and
then
provide analytics on historical data.
Both suggestions are IMO difficult to implement, just for the benefit of generating historic data. Not mentionning the huge overhead.
-- Marc Delisle http://infomarc.info
Hi,
We can access the MySQL log?
You mean the binary log? http://forge.mysql.com/wiki/MySQL_Internals_Binary_Log
If you find a way to do that via a command sent from mysqli_query() or mysql_query(), tell me.
Hi,
We can use one of the many logs available here: http://dev.mysql.com/doc/refman/4.1/en/server-logs.html
Can use fopen() to read through the logs and generate data.
You are thinking about a process external to phpMyAdmin here, I guess. This is not in the scope of the GSoC projects for phpMyAdmin.
Or I think the way of creating a separate PHP library which can capture all data upto a certain extent would do it too. We will anyway have to maintain the data to build the graphs.
I don't get your point. What would be calling this PHP library in order to capture this data? You mean all data passing through phpMyAdmin? This does not reflect the complete server activity.
And the user might turn it off or on as per his wish as and whenever needed for diagnose basis.
Thanks