== Quote from Peter H. Coffin (hellsop@ninehells.com)'s article
> On Wed, 19 Dec 2007 16:26:30 -0000, slambert wrote:
> >>> It works fine in local and in the development server. We have crash only
> >>> in
> >>> the production server, with exactly the same datas.
> >>>
> >>> Weird....
> >>
> >> So tell us what is different between the servers. "Nothing" is clearly
> >> the wrong answer.
> >
> > development server :
> > MySQL - 5.0.21-log
> > phpMyAdmin - 2.8.0.4
> >
> > production server:
> > Server version: 5.0.24-Max-log
> > phpMyAdmin - 2.11.2.2
> >
> > The 2 of them are under a Linux, but I can't said wich one.
> >
> > More, in local in my windows machine, the same queries works with the same
> > database and the same datas:
> > Server version: 5.0.41-community-nt
> > phpMyAdmin - 2.11.2.1
> So the dev server and the production server are approximately the same,
> plus or minus max extensions.
> > I konw that's bad to do not work with the same environment, but I asked for
> > a mysql5 and that's what I had in development and in production. I
> > discovered the production one a couple of weeks ago.
> >
> > another example of failing query:
> > update institution SET Gal_Nom = REPLACE(Gal_Nom ,'é','é')
> >
> > See++
> Okay, next I think we should look at is SHOW CREATE TABLE institution;
> output. I am thinking that the row size problem that was talked about
> earlier is fairly likely, but what the table looks like will prove or
> disprove this.

sorry to bug in your conversation but error 139 indicates too big of a row. don't
know if this helps.
--
POST BY: lark with PHP News Reader ;o)