Bug#576412: [php-maint] Bug#576412: Bug#576412: php5: Please add MySQL native driver "mysqlnd" support for PHP 5.3.x

2010-04-05 Thread Alexander Schories
Hello Ondrej,


i understand that compression and SSL for MySQL are yet missing.
However, they might not be used widely on most debian installations -
but they are still very important features, i agree.

Every project includes marketing. And not only some people see
advantages in mysqlnd.

I also haven't expected to see this feature in the upcoming debian
release, but in the experimental/unstable trees.

But if the majority of all maintainers chose to wait with an
implementation even there, i understand it's for a serious reason and
completely accept this decision. :)

Thank you once again


Alexander Schories
Tuebingen, Germany



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#576412: [php-maint] Bug#576412: Bug#576412: php5: Please add MySQL native driver "mysqlnd" support for PHP 5.3.x

2010-04-05 Thread Ondřej Surý
On Mon, Apr 5, 2010 at 09:41, Alexander Schories  wrote:
> Hi Raphael,
>
>
> first of all thank you for the fast reply.
>
> Could you please - at least once - give a proof for what changed so
> badly, instead of repeatingly using the term "nonsense", please? I mean,
> have you at least tried mysqlnd?
>
> What *exactly* is missing or breaks?

Just read the webpage you mentioned:

Q: Does it offer all functionality of the MySQL Client Library?

No, compression and SSL support are currently missing. We have started
to work on compression support, SSL will come later.

* and *

The current release covers the functionality of the libmysql beside
some functions that are marked as experimental in the PHP
documentation.

-- ** --
So:

- doesn't break current PHP5 extensions, such as php5-mysql(i) or
PDO_MYSQL at all!

Nonsense - it does break API.

- comes with a superior license: PHP license, no need for FLOSS
Exception any more

Nonsense, you don't need any exception to link with libmysqlclient in
PHP. And there is existing exception in libmysqlclient.

- it's native: uses PHP memory management, supports PHP memory limit
- it's oh so native: keeps every row only once in memory, with
libmysql you have it twice in memory

Existing mysql extensions use memory limit as well. If there is
performance bottleneck or unoptimal behaviour in mysql extension, it
needs to be fixed there.

- comes with new features: keeps a long list of performance related
statistics for bottle-neck analysis
- comes with even more new features: persistent connections for ext/mysqli

So what? Two new features? Why they didn't add that to existing extensions?

- offers considerable performance improvements compared to
php5-mysql(i), for example when fetching buffered result sets,
client-side result set cache (pre-alpha design study in Bazaar)

So it will be fast, but not really tested? Ah, great.

- it's easier to compile: no more linking against libmysql
- it's yet easier to compile: no need to have libmysql on the PHP build host

Ah, more nonsense.

The webpage has more marketing stuff than technical.

It's yet again reinventing wheel (shared library).

Ondrej
-- 
Ondřej Surý 
http://blog.rfc1925.org/



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org