Hi Marc,
As I can understand the tracking is implemented in the php code. So if I run a query directly in the database without using phpMyAdmin functions, the trucking will not function. However my idea is not the tracking, I want to keep table row versions.
So here is what I think:
1. Add a new tab for a database table (like Tracking) -- Let's call it Revisions 2. Allow the user to enable revision control for that table -- user can select which table fields need to be kept under control 3. Using php it will create new table called Table_history and will add a mysql trigger on Table to add the row changes to the history table. So in this case it will be implemented in the database, not in the php code. So let's say I'm running a joomla site and I want to keep jos_content table versions. I go to phpMyAdmin create a revision for that table. So when I edit my content through the joomla administration area, which is not running on phpMyAdmin php functions, it will still keep revisions for that table.
Let me know your thoughts.
Regards,
Edvard
In phpMyAdmin 3.3 we already have changes tracking; we expect would-be participants to be familiar with the current phpMyAdmin version.
How would your project be different than what is currently in version 3.3?
-- Marc Delisle http://infomarc.info
On Mon, Mar 22, 2010 at 3:36 PM, Edvard Ananyan edo888@gmail.com wrote:
Hi,
As you may already know Joomla! didn't participate in GSoC this year.
Last year I was a GSoC student doing a project for Joomla: http://jwcp.googlecode.com/ Here you can find my last year's proposal: http://edo.webmaster.am/proposals/11
This year I want to extend it and make possible to select tables from the database which can be kept under revision control with the help of mysql triggers.
Currently in Working Copy I'm using a "spy" implemented with mysql triggers which can log the changes made on the table.
What do you think can the versioning of mysql tables become a project for phpMyAdmin?
Regards,
Edvard