Hi all
I've just set up another database to demo server - Drizzle. At first attempt phpMyAdmin did not work at all, but after few fixes (basically disabling all charsets/collation handling we do on connect), we're at least able to connect and show the interface with some databases and tables.
However there is much more things to fix (for example phpMyAdmin does not see all tables for some reason) and definitely more to test. However the question is if we want to officially support Drizzle and put some effort into it.
You can try phpMyAdmin with Drizzle here: http://demo.phpmyadmin.net/master-config/?server=3
More information about Drizzle: http://drizzle.org/
Michal Čihař a écrit :
Hi all
I've just set up another database to demo server - Drizzle. At first attempt phpMyAdmin did not work at all, but after few fixes (basically disabling all charsets/collation handling we do on connect), we're at least able to connect and show the interface with some databases and tables.
However there is much more things to fix (for example phpMyAdmin does not see all tables for some reason) and definitely more to test. However the question is if we want to officially support Drizzle and put some effort into it.
I think that current phpMyAdmin's code is too MySQL-oriented and that this product should remain an interface for MySQL only. Another point is the "My" in phpMyAdmin and the signal it gives to the community.
I have nothing against Drizzle but I think that the phpMyAdmin team should remain focussed on MySQL. Anybody can fork the phpMyAdmin's code to take another direction but I certainly do not have free time to be part of this other team.
However I am open to diverging opinions :)
Hi
Dne Thu, 21 Oct 2010 04:55:19 -0400 Marc Delisle marc@infomarc.info napsal(a):
I think that current phpMyAdmin's code is too MySQL-oriented and that this product should remain an interface for MySQL only. Another point is the "My" in phpMyAdmin and the signal it gives to the community.
Th "MySQL only" has already one problem called MariaDB :-).
I have nothing against Drizzle but I think that the phpMyAdmin team should remain focussed on MySQL. Anybody can fork the phpMyAdmin's code to take another direction but I certainly do not have free time to be part of this other team.
We definitely should clearly state what we want to support and what not. MySQL, MariaDB and Drizzle still share fair amount of code and they all use same binary protocol and quite similar SQL language, so they are not that different.
MariaDB adds some features compared to MySQL (some of that will be part of future MySQL releases, but some not), do we want to support these?
The most important changes for Drizzle would be actually do disable some functions, which are not present there (like the charset/collation thing I've pushed to git, though maybe too fast).
Indeed aiming at full compatibility with Drizzle for 3.4 would not make sense and would shift the release too far away. The only thing which might make sense is to fix basic functionality, with no official support for Drizzle.
PS: Some changes, which would be needed for full Drizzle support, will be as well needed for upcoming MySQL features. Eg. Drizzle authentication plugins and MySQL's pluggable authentication system (well if that is ever going to be open sourced). But that's definitely not something for near future.
Michal Čihař a écrit :
Hi
Dne Thu, 21 Oct 2010 04:55:19 -0400 Marc Delisle marc@infomarc.info napsal(a):
I think that current phpMyAdmin's code is too MySQL-oriented and that this product should remain an interface for MySQL only. Another point is the "My" in phpMyAdmin and the signal it gives to the community.
Th "MySQL only" has already one problem called MariaDB :-).
The difference being that in our doc we state support for MySQL and we don't mention MariaDB.
I have nothing against Drizzle but I think that the phpMyAdmin team should remain focussed on MySQL. Anybody can fork the phpMyAdmin's code to take another direction but I certainly do not have free time to be part of this other team.
We definitely should clearly state what we want to support and what not. MySQL, MariaDB and Drizzle still share fair amount of code and they all use same binary protocol and quite similar SQL language, so they are not that different.
MariaDB adds some features compared to MySQL (some of that will be part of future MySQL releases, but some not), do we want to support these?
Do we have volunteers to support these?
The most important changes for Drizzle would be actually do disable some functions, which are not present there (like the charset/collation thing I've pushed to git, though maybe too fast).
I was under the impression that Drizzle avoided the SHOW commands (which we use a lot).
Indeed aiming at full compatibility with Drizzle for 3.4 would not make sense and would shift the release too far away. The only thing which might make sense is to fix basic functionality, with no official support for Drizzle.
PS: Some changes, which would be needed for full Drizzle support, will be as well needed for upcoming MySQL features. Eg. Drizzle authentication plugins and MySQL's pluggable authentication system (well if that is ever going to be open sourced). But that's definitely not something for near future.
Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Hi
Dne Thu, 21 Oct 2010 08:09:13 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Thu, 21 Oct 2010 04:55:19 -0400 Marc Delisle marc@infomarc.info napsal(a):
I think that current phpMyAdmin's code is too MySQL-oriented and that this product should remain an interface for MySQL only. Another point is the "My" in phpMyAdmin and the signal it gives to the community.
Th "MySQL only" has already one problem called MariaDB :-).
The difference being that in our doc we state support for MySQL and we don't mention MariaDB.
Yes, but I don't think we want to state that we do not support MariaDB. Simply because it works and is compatible with MySQL.
I have nothing against Drizzle but I think that the phpMyAdmin team should remain focussed on MySQL. Anybody can fork the phpMyAdmin's code to take another direction but I certainly do not have free time to be part of this other team.
We definitely should clearly state what we want to support and what not. MySQL, MariaDB and Drizzle still share fair amount of code and they all use same binary protocol and quite similar SQL language, so they are not that different.
MariaDB adds some features compared to MySQL (some of that will be part of future MySQL releases, but some not), do we want to support these?
Do we have volunteers to support these?
Well we do support some of that already (eg. PBXT). And some of the MariaDB 5.2 features will come with MySQL later as well (eg. virtual columns and pluggable authentication to mention some prominent features).
The most important changes for Drizzle would be actually do disable some functions, which are not present there (like the charset/collation thing I've pushed to git, though maybe too fast).
I was under the impression that Drizzle avoided the SHOW commands (which we use a lot).
Maybe some of them, but SHOW TABLES, SHOW DATABASES and SHOW FIELDS do exist (however not SHOW FULL FIELDS). I didn't investigate more, I was just inspired by LWN.net article about MySQL, MariaDB and Drizzle and wanted to see what would be actually working.
Michal Čihař a écrit :
Hi
Dne Thu, 21 Oct 2010 08:09:13 -0400 Marc Delisle marc@infomarc.info napsal(a):
Michal Čihař a écrit :
Hi
Dne Thu, 21 Oct 2010 04:55:19 -0400 Marc Delisle marc@infomarc.info napsal(a):
I think that current phpMyAdmin's code is too MySQL-oriented and that this product should remain an interface for MySQL only. Another point is the "My" in phpMyAdmin and the signal it gives to the community.
Th "MySQL only" has already one problem called MariaDB :-).
The difference being that in our doc we state support for MySQL and we don't mention MariaDB.
Yes, but I don't think we want to state that we do not support MariaDB. Simply because it works and is compatible with MySQL.
Eventually we will have to clarify our support of MariaDB, mentionning which version and what kind of support.
I have nothing against Drizzle but I think that the phpMyAdmin team should remain focussed on MySQL. Anybody can fork the phpMyAdmin's code to take another direction but I certainly do not have free time to be part of this other team.
We definitely should clearly state what we want to support and what not. MySQL, MariaDB and Drizzle still share fair amount of code and they all use same binary protocol and quite similar SQL language, so they are not that different.
MariaDB adds some features compared to MySQL (some of that will be part of future MySQL releases, but some not), do we want to support these?
Do we have volunteers to support these?
Well we do support some of that already (eg. PBXT). And some of the MariaDB 5.2 features will come with MySQL later as well (eg. virtual columns and pluggable authentication to mention some prominent features).
I don't view PBXT as a MariaDB feature, it's just that they package this engine with their product.
The most important changes for Drizzle would be actually do disable some functions, which are not present there (like the charset/collation thing I've pushed to git, though maybe too fast).
I was under the impression that Drizzle avoided the SHOW commands (which we use a lot).
Maybe some of them, but SHOW TABLES, SHOW DATABASES and SHOW FIELDS do exist (however not SHOW FULL FIELDS). I didn't investigate more, I was just inspired by LWN.net article about MySQL, MariaDB and Drizzle and wanted to see what would be actually working.
What about http://pecl.php.net/package/drizzle ? I guess that proper support should include using this wrapper to libdrizzle.
Hi
Dne Thu, 21 Oct 2010 09:36:52 -0400 Marc Delisle marc@infomarc.info napsal(a):
I don't view PBXT as a MariaDB feature, it's just that they package this engine with their product.
Well there is not much more visible changes from phpMyAdmin perspective than new (or improved) storage engines in MariaDB. The rest are mostly performance improvements.
What about http://pecl.php.net/package/drizzle ? I guess that proper support should include using this wrapper to libdrizzle.
As Drizzle currently speaks MySQL binary protocol, there is no need for that. It might be however needed in future (they plan to develop own binary protocol).
-
Marc Delisle -
Michal Čihař