Hello Jim,
> > > sounds like you are using the wrong value for the length of a utf8
> > > field, where the number of characters is being divided by the max
> > > character length. (10 / 3 = 3, 80 / 3 = 26)
> > >
> > > or it could be the server returning the wrong length. use "mysql
> > > --column-
At 2:57 PM -0400 4/16/08, Jim Winstead wrote:
On Fri, Apr 11, 2008 at 08:54:26AM +0200, Martijn Tonies wrote:
Hello Jim,
> On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> > It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> > checked).
> >
> > Instea
On Fri, Apr 11, 2008 at 08:54:26AM +0200, Martijn Tonies wrote:
> Hello Jim,
>
>
> > On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> > > It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> > > checked).
> > >
> > > Instead of returning the full data, the first
Hello Jim,
> On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> > It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> > checked).
> >
> > Instead of returning the full data, the first two columns are cut off at
3
> > characters,
> > while the "comment" column is
On Thu, Apr 10, 2008 at 09:32:43AM +0200, Martijn Tonies wrote:
> It seems that SHOW ENGINES fails on MySQL 5.0.51a (community edition
> checked).
>
> Instead of returning the full data, the first two columns are cut off at 3
> characters,
> while the "comment" column is cut off at 26 characters.
Sorry, a bit too hasty --
It seems to work fine in the command line client!
Has the wire protocol changed somehow?
Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.
