This page lists feedback entries tagged with database sorted on creation date
After having a look at the code, I think it would be better if all database operations were stored in a class.
The class Db exists, but, outside this class, there are calls to mysql_* functions. This is a problem for porting phpMyVisites to other DBMS.
I may help doing this if you want.
p.s : I could not find any matching category for this post, so I put it here.
It would interesting to be able to "purge" old data in phpMyVisites, when the database gets to big for example.
You could purge datas such as "referers", "visitor configuration" or "pages view details" but keep the 'numbers' such as visits, no of page views, etc. ; we could keep the numbers simply because the size is very small in database.
Currently this is not really possible to implement this with the current architecture, but we would like to know if this feature is worth the job.
It would be useful to be able to backup the phpmyvisites tables in a .tar.gz file on the server. Then you could download this file and save it on your computer. It would make it easy to upload this database to a new server, or to restore it after a server crash.