Hi Sir

Sorry I was not aware of this feature but yes, its quite hidden. Yes, that can be one way of doing it. I was just testing the console and found it is logging all of the queries that is taking place. So another way of implementing version control is having one base database as static and logging all of the queries that is taking place. This can even be done using a text file and when user wishes to return back to some version we can just execute the queries that have taken place between the static database and the version which user demands. This way memory will also be saved and eliminate requirement of saving a snapshot of databases. Agreed it will take a little more time to recover but there are more positives than negatives. I hope this is feasible.

What I am trying to propose is bringing all features as commands in console and not restricting it to just SQL queries. Console is one of the best introductions to phpMyAdmin and can be taken to greater potential.

Please let me know if this can be worked and can be accepted as a GSoC project and also the flaws.

Regards,
Manraj Singh Grover
Secretary, IEEE NSIT
Connect on LinkedIN
Ph. +91-9811040427

On Tue, Mar 3, 2015 at 11:12 PM, Marc Delisle <marc@infomarc.info> wrote:
Manraj Grover a écrit :
> Hi
>
> I would like to extend the functionalities of the present Console in
> phpMyAdmin as a part of GSoC project. I was testing current one and found
> the following issues:

Hi,
thanks for sharing your idea.
>
> UI improvements:
>> The option tab and console pointer are too far away from each other
> leading to great mouse traversing time. It should be close enough and not
> at the other end given a lot of space is available to use.
>> Keyboard use: Escape to close is another thing missing(Minute fix)
>> On clicking "Options" a huge div for settings open. Given options are
> currently low in number and there is not a lot of text to show, it should
> be reduced.Again it increases mouse traversing time.
>
> Currently the console is used for SQL queries. I would like to propose
> following additions to it.
>
>> Introduction of version control. (git like feature)
> This is a much needed change. How many times it has happened one single
> query and your data is lost forever?
> This is help keep track of previously saved version of database as a backup
> so that user can restore and start working on it if and when required.

Where do you plan to keep the backup? In the database itself, I guess?
If so, how will this scale?

And do you plan an automatic save?

Regarding this feature, are you aware that phpMyAdmin already has a
tracking mechanism?

http://docs.phpmyadmin.net/en/latest/config.html?highlight=tracking#cfg_Servers_tracking


>
>> Introduction of opening tabs and filling fields using console
> Again another feature that gives console power to do things.
>
>> Introduction of "help" command
> It will help users how to use console for example one can execute "help"
> for complete help or "help select" to know the details
>
>> Run, preview and then only apply changes to database
> Another safety feature that can be included in console making console more
> powerful.
>
> The possibilities are endless. Lets discuss this over and create a working
> model.
>
> Regards,
> Manraj Singh Grover
> Secretary, IEEE NSIT
> Connect on LinkedIN <http://in.linkedin.com/in/manrajsinghgrover/>
> Ph. +91-9811040427
>



--
Marc Delisle (phpMyAdmin)

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel