Just trying to work out why my footprint was bigger than I expected running
the windows 5.3.0-dev and I've got mysqlnd installed when I don't need it. How
do I get rid of it or am I going have to compile my own builds in future?
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Lester Caine wrote:
Just trying to work out why my footprint was bigger than I expected
running the windows 5.3.0-dev and I've got mysqlnd installed when I
don't need it. How do I get rid of it or am I going have to compile my
own builds in future?
It's on by default on windows, so you'll have to compile your own builds
if you don't want it - use the --without-mysqlnd flag on windows
Elizabeth M Smith wrote:
Lester Caine wrote:
Just trying to work out why my footprint was bigger than I expected
running the windows 5.3.0-dev and I've got mysqlnd installed when I
don't need it. How do I get rid of it or am I going have to compile my
own builds in future?It's on by default on windows, so you'll have to compile your own builds
if you don't want it - use the --without-mysqlnd flag on windows
Another reason not to switch to 5.3? :(
Any particular reason why it's been changed - I can't see anything I need it for.
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Elizabeth M Smith wrote:
Lester Caine wrote:
Just trying to work out why my footprint was bigger than I expected
running the windows 5.3.0-dev and I've got mysqlnd installed when I
don't need it. How do I get rid of it or am I going have to compile my
own builds in future?It's on by default on windows, so you'll have to compile your own builds
if you don't want it - use the --without-mysqlnd flag on windowsAnother reason not to switch to 5.3? :(
Come on. Mysql has been always been enabled by default.
Any particular reason why it's been changed - I can't see anything I need it
for.
It is the main library used by all mysql modules, it replaces libmysql.
Cheers,
Pierre Joye wrote:
Elizabeth M Smith wrote:
Lester Caine wrote:
Just trying to work out why my footprint was bigger than I expected
running the windows 5.3.0-dev and I've got mysqlnd installed when I
don't need it. How do I get rid of it or am I going have to compile my
own builds in future?It's on by default on windows, so you'll have to compile your own builds
if you don't want it - use the --without-mysqlnd flag on windows
Another reason not to switch to 5.3? :(Come on. Mysql has been always been enabled by default.
NO Mysql was REMOVED as the default in 5.0.0 after lots of requests from
those of us who don't want it loaded. There was a democratic decision to
remove it.
Any particular reason why it's been changed - I can't see anything I need it
for.It is the main library used by all mysql modules, it replaces libmysql.
And should only be load if MySQl is required ...
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Come on. Mysql has been always been enabled by default.
NO Mysql was REMOVED as the default in 5.0.0 after lots of requests from
those of us who don't want it loaded. There was a democratic decision to
remove it.
NO. MySQL was no longer bundled from 5.0.0 because MySQL AB went GPL on
us. The mysqlnd library is their resolution for that problem.
- Steph
Steph Fox wrote:
Come on. Mysql has been always been enabled by default.
NO Mysql was REMOVED as the default in 5.0.0 after lots of requests
from those of us who don't want it loaded. There was a democratic
decision to remove it.NO. MySQL was no longer bundled from 5.0.0 because MySQL AB went GPL
on us. The mysqlnd library is their resolution for that problem.
MySQL was replaced by SQLite as the default database in the very first release
of 5.0.0 http://www.php.net/ChangeLog-5.php#5.0.0b1
The PRIMARY reason was because of the number of non MySQL users who requested
that. CURRENTLY the default sql connection is SQLite so there is no need to
add back in another option. The changes to the licence conditions just made
the CHANGE of database easier ;)
MySQL should NOT be loaded by default as well as SQLite.
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
MySQL was replaced by SQLite as the default database in the very first
release of 5.0.0 http://www.php.net/ChangeLog-5.php#5.0.0b1
Yes.
The PRIMARY reason was because of the number of non MySQL users who
requested that.
No. Will you please stop trying to rewrite history. There was an outcry when
MySQL was unbundled - you were probably the only PHP user who was happy
about it :)
- Steph
Steph Fox wrote:
MySQL was replaced by SQLite as the default database in the very first
release of 5.0.0 http://www.php.net/ChangeLog-5.php#5.0.0b1Yes.
The PRIMARY reason was because of the number of non MySQL users who
requested that.No. Will you please stop trying to rewrite history. There was an outcry
when MySQL was unbundled - you were probably the only PHP user who was
happy about it :)
And every other non-MySQL database user.
http://uk.php.net/manual/en/faq.databases.php#faq.databases.mysql.php5
outlines some of the 'problems' but I can't find the other requests in the
list archive. Although I have found ones from 2003 where I tell people HOW to
enable MySQL again. I think the initial problem was that the extensions were
not available for MySQL initially and took a while to appear?
WHY can't MySQL simply stay in the extensions with the rest of the database
extensions. Why does it have to have preferential treatment? If applications
need a little database to work they use SQLite otherwise we load a suitable
alternative of our choice!
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Pierre Joye wrote:
Elizabeth M Smith wrote:
Lester Caine wrote:
Just trying to work out why my footprint was bigger than I expected
running the windows 5.3.0-dev and I've got mysqlnd installed when I
don't need it. How do I get rid of it or am I going have to compile my
own builds in future?It's on by default on windows, so you'll have to compile your own builds
if you don't want it - use the --without-mysqlnd flag on windowsAnother reason not to switch to 5.3? :(
Come on. Mysql has been always been enabled by default.
NO Mysql was REMOVED as the default in 5.0.0 after lots of requests from
those of us who don't want it loaded. There was a democratic decision to
remove it.
I was not clear. Mysql has been (and still is) always enabled and
available by default in our Windows binaries.
It is the main library used by all mysql modules, it replaces libmysql.
And should only be load if MySQl is required ...
Agreed, but I do not maintain mysqlnd (and not willing to :), can you
open a bug about that please?
Cheers,
Pierre
I was not clear. Mysql has been (and still is) always enabled and
available by default in our Windows binaries.
Not now, and not for a very long time.
Agreed, but I do not maintain mysqlnd (and not willing to :), can you
open a bug about that please?
It's not a bug. It was a democratic decision taken in the early days of 5.3.
- Steph
Steph Fox wrote:
I was not clear. Mysql has been (and still is) always enabled and
available by default in our Windows binaries.Not now, and not for a very long time.
Agreed, but I do not maintain mysqlnd (and not willing to :), can you
open a bug about that please?It's not a bug. It was a democratic decision taken in the early days of
5.3.
LINKS?
In fact I can see YOU commenting that it should not be enabled by default!
But that was 2007 - I see no agreement that it should be later ?
I will be opening a bug - if only to flag the need for a switch to disable it
if it's not required.
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
In fact I can see YOU commenting that it should not be enabled by default!
But that was 2007 - I see no agreement that it should be later ?
mysqlnd needs to be built-in statically.
I will be opening a bug - if only to flag the need for a switch to disable
it if it's not required.
We have that. --disable-mysqlnd.
- Steph
I was not clear. Mysql has been (and still is) always enabled and
available by default in our Windows binaries.Not now, and not for a very long time.
Can we stop with the nitpicking? mysql has been available.
Agreed, but I do not maintain mysqlnd (and not willing to :), can you
open a bug about that please?It's not a bug. It was a democratic decision taken in the early days of 5.3.
To have it by default, to have it always even when using --disable-all
and no mysql extensions are enabled? yes, it is bug.
--
Pierre
I was not clear. Mysql has been (and still is) always enabled and
available by default in our Windows binaries.Not now, and not for a very long time.
Can we stop with the nitpicking? mysql has been available.
To paraphrase Meatloaf, one out of three ain't bad :)
Agreed, but I do not maintain mysqlnd (and not willing to :), can you
open a bug about that please?It's not a bug. It was a democratic decision taken in the early days of
5.3.To have it by default, to have it always even when using --disable-all
and no mysql extensions are enabled? yes, it is bug.
Can you build it as shared? I can't actually get --disable-all to work here,
it keeps shouting about objects-out-dir being 'no'.
- Steph
Steph Fox wrote:
Can you build it as shared? I can't actually get --disable-all to work
here, it keeps shouting about objects-out-dir being 'no'.
- Steph
Ah, shoot, the disable-all thing... that's a configure bug steph, and I
have a patch to fix it sitting around here somewhere....
Elizabeth
Any particular reason why it's been changed - I can't see anything I need
it for.
The other million or so who do.
- Steph