[Phpmyadmin-devel] Suggestions for Import/Export Changes

Derek Schaefer derek.schaefer at gmail.com
Wed Jul 1 17:19:28 CEST 2009


On Wed, Jul 1, 2009 at 3:32 AM, Michal Čihař<michal at cihar.com> wrote:
> Hi
>
> Dne Mon, 29 Jun 2009 14:35:33 -0500
> Derek Schaefer <derek.schaefer at gmail.com> napsal(a):
>
>> First, possibilities for the new import interface. For those who don't
>> know much about my GSoC project, one of the goals was to create an
>> intermediary interface for editing the structure of a new
>> database/table set that was deduced from some import data. Via this
>> interface the structure is to be altered and changed as necessary
>> (dropping tables, changes keys, etc.) and once the user is satisfied,
>> it is created and the data (now adapted to the new structure) in
>> inserted. This involved storing all the data from the import in a PHP
>> session so the source wouldn't have to be reanalyzed after the user
>> made edits to the structure. I have been having some second thoughts
>> regarding such an interface. Depending on the size of the import, the
>> PHP session could take up a considerable amount of memory. Also, all
>> database and table options are editable after creation via the current
>> regular db/table interface, therefore I believe the intermediary
>> interface would be redundant at best, and counterintuitive as worst.
>> All the while being rather inefficient. I find that directing the user
>> towards the newly created database and/or tables via a notification
>> after a successful import is simple, effective, and vastly more
>> efficient.
>
> It might be an option. However converting some data later might be
> problematic, but I fail to find good example right now :-).

Alright, I'll run some tests and see if there are any problems. Should
I move forward on this basis for the time being? I can always add the
new interface(s) later if they are deemed desirable.

>> Second, I would like to propose a new XML export format to better
>> support my new import features. This new format will present the
>> option to export the SQL creation code for each of the exported tables
>> in the manner outlined below:
>>
>> <?xml version="1.0" encoding="utf-8" ?>
>> <!--
>> -
>> - phpMyAdmin XML Dump
>> - ... etc. etc. etc.
>> -->
>>
>> <pma_xml_export version="1.0"
>> xmlns:pma="http://www.phpmyadmin.net/some_doc_url/">
>>     <pma:structure>
>>         <pma:db_name>
>>             <pma:tbl_name_1>CREATE TABLE `tbl_name_1`...</pma:tbl_name_1>
>
> Please make it proper XML then and do not (re)introduce variable tag
> names.
>
> <pma:structure>
>  <pma:db name="databaze">
>     <pma:table name="tabulka">CREATE...</pma:table>
>     ...
>     <pma:view name="pohled">CREATE...</pma:view>
>     <pma:trigger name="procedura">...</pma:trigger>
>  </pma:db>
> </pma:structure>
Splendid, will do.

> --
>        Michal Čihař | http://cihar.com | http://phpmyadmin.cz
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Phpmyadmin-devel mailing list
> Phpmyadmin-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
>
>




More information about the Developers mailing list