GSoC 2015 : Weekly Report #6 : RFE #342 & RFE#1060
Tasks worked upon:
Scheduled Deadline: 12th July
Completed on: NA
1. The RFE#342 suggests that we provide an option to export objects inside a database/ server as separate files.
At present, while exporting a database/ server, the form at server_export.php or db_export.php is submitted to export.php, where various post parameters are set and functions from export.lib.php are called using those appropriate parameters.
Now, I added a checkbox on db_export.php and server_export.php with a label as ‘Export Tables/ Databases as separate files’. When checked, it forces the compression method to go to ‘zipped’ as only Zip compression is supported for separate file export.
Now, while exporting a server, it is simple, as each database will have one file each. But the catch is while exporting a database as it may have views, procedures, functions, triggers, indexes, auto_increments etc.
Thus, with a discussion with my mentor, Isaac, we decided the structure of the export zip as :
a. Tables exported as dbName_tbl_tblName.sql
b. Views exported as dbName_view_viewName.sql
c. All routines grouped and exported as dbName_routines.sql
d. All triggers grouped and exported as dbName_triggers.sql
e. Indexes, Auto increments and other information grouped and exported as dbName_extra.sql
All formats of exports such as SQL, Doc, LaTex etc. are supported.
The PR is at the testing phase and is not merged yet, but will be merged soon.
2. The description about RFE#1060 is available in my previous blog post here 
The decision about this has been made that we will add a new table in configuration storage and store the designer settings/ preferences there.
The related PR is still under review and testing and will be merged soon.
Implemented with: NA
 : https://github.com/phpmyadmin/phpmyadmin/pull/1744
 : https://devenbansod.wordpress.com/2015/06/15/gsoc-2015-weekly-report-5-rfe-1594-rfe1060/
 : https://github.com/phpmyadmin/phpmyadmin/pull/1737