[Phpmyadmin-devel] [GSoC] OO PMA project proposals

[Dieter Adriaenssens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Michal,

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (MingW32)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.10)

iEYEARECAAYFAkurZ/4ACgkQZGJbiPqZM6MMUwCeMVQWfpggUbbJYbyl+ZLTmI3e
7AUAn2ugPx+xRegLlr/nZwwf6gKtZ7UQ
=lqWn
-----END PGP SIGNATURE-----

2010/3/25 Michal Čihař <michal at cihar.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi
>
> Dne Thu, 25 Mar 2010 11:06:06 +0100
> Dieter Adriaenssens <dieter.adriaenssens at gmail.com> napsal(a):
>
>> I agree that Export is a good candidate to rewrite in OO, for several reasons :
>>
>> * It's a stand alone module, nothing major depends on it (I think).
>
> Well SQL export is used in several other places (table move/copy and I
> think also some synchronisation or other recently introduced feature
> uses it).
>

Table move/copy uses similar logic, but it's not shared with (except
for some core functions) or depending on export. (I would have to
check the code to be sure, but I've made some changes to both and I
recall it was seperate code)
But it is a good idea to use modified SQL export/import modules to
copy a database or table. (modification should be to generate an sql
export with renamed database/table names).
I'm not sure if this mechanism should always be applied for
moving/renaming databases or tables. This can more easily be done with
an ALTER statement, unless you move a table to another database of
course.
But this goes beyond the scope of Edouards proposal, but it might be a
nice application of an OO-ified export module. ;)

I didn't know about synchronisation and other features relying on the
export module.

Kind regards,

Dieter