mysql5 + php5

People seem to be avoiding both MySQL 5 and php 5, is there really a
reason for this other than the troubles everyone has had at some point
upgrading MySQL from 3.x to 4.x. I'm glad I didn't attempt that one on a
Live systems.

Or are you all just waiting for your ISP to take them up before you are
able to move to them.

From google there aren't a lot of major problems reported for php5, but
the type of problems have been enough to put off those who run a live
system. Though in 5.1.0/1 those major areas seem to have been sorted out.

Oh well, some of us have to be pioneers, march at the frount and brave the
future. You can tell which ones we are because we tend to have crooked
noses and walk with a limp.

The change to using references by default for objects was (IMHO) a
great step forward for PHP (but a lot of the other OO stuff just seems
to be there to make PHP look like Java).

While the PHP 5.x releases are settling down now, I still find it
worrying the level of debate over what is actually "broken" vs "not
backwardly compatible". While (as with my comment above) sometimes
there is no other other choice, anything which damages backward
compatability should be strongly discouraged - particularly with a
programming language in widesparead usage.

I'd find it hard to justify a MySQL upgrade unless I needed the new
clustering features.

C.

On Fri, 02 Dec 2005 04:35:34 -0800, C. wrote:

> The change to using references by default for objects was (IMHO) a
> great step forward for PHP (but a lot of the other OO stuff just seems
> to be there to make PHP look like Java).
>
> While the PHP 5.x releases are settling down now, I still find it
> worrying the level of debate over what is actually "broken" vs "not
> backwardly compatible". While (as with my comment above) sometimes
> there is no other other choice, anything which damages backward
> compatability should be strongly discouraged - particularly with a
> programming language in widesparead usage.

I agree there, it used to be that new releases had to ensure backward
compatibility, these days it seems quite normal to simply make changes and
drop support for current code.

> I'd find it hard to justify a MySQL upgrade unless I needed the new
> clustering features.
>
> C.

The stored procedures look well put together on paper, I haven't used the
MySQL version of this so can't say how well it works in practice but from
a cursory glance it looks simmilar in use to postgres or the other major
db engines.

... and it came to pass that C. <colin.mckinnon@gmail.com> uttered forth:
>I'd find it hard to justify a MySQL upgrade unless I needed the new
>clustering features.

Doesn't mysql5 support subselect and XML output? (that mysql4
didn't)...?

--

"Dungeon" Dave

Quoth 'Dungeon' Dave:

> Doesn't mysql5 support subselect and XML output? (that mysql4
> didn't)...?

....and stored procedures and probably some other stuff too.

C.