Mailing List Archive


Back to the month index Back to the list index
Richard Duncan Lennerts (lenne-rd@ee.uwa.edu.au)
Wed, 30 Apr 1997 11:42:58 +0800 (WST) 

Date: Wed, 30 Apr 1997 11:42:58 +0800 (WST)
From: Richard Duncan Lennerts <lenne-rd@ee.uwa.edu.au>
Subject: Re: [mSQL] Bug: Relational Text operations.  Coredumps..
Message-Id: <Pine.SGI.3.95.970430114006.7568Q-100000@onyx>

I have had a similar problem in the past. I reported this to Bambi and he
said it had something to do with the way indexes work. This was in beta2 I
think and all seemed ok in later versions. However, try exporting your
database, dropping it, recreating it and then import your data again, as
this has worked form me.

A fairly crude solution, but hey it's still in beta.

Regards,

Richard Lennerts

On Tue, 29 Apr 1997, David Apfelbaum wrote:

> I think I've found a bug with mSQL 2.0 Beta 6.
>
> More or less, relational joins between two text fields seem to either
> fail to return what they should, or trigger a msql2d "bad signal"
> coredump.
>
> Example:
>
> mSQL > create table z1 ( string text(10) )\g
> Query OK. 1 row(s) modified or retrieved.
>
> mSQL > create table z2 ( string text(10) )\g
> Query OK. 1 row(s) modified or retrieved.
>
> mSQL > insert into z1 values ( 'foo' )\g
> Query OK. 1 row(s) modified or retrieved.
>
> mSQL > insert into z2 values ( 'foo' )\g
> Query OK. 1 row(s) modified or retrieved.
>
> mSQL > select z1.string, z2.string from z1, z2 where z1.string = z2.string \g
> Query OK. 0 row(s) modified or retrieved.
> +------------+------------+
> | string | string |
> +------------+------------+
> +------------+------------+
>
> mSQL > select * from z1\g
> Query OK. 1 row(s) modified or retrieved.
> +------------+
> | string |
> +------------+
> | foo |
> +------------+
>
> mSQL > select * from z2\g
> Query OK. 1 row(s) modified or retrieved.
> +------------+
> | string |
> +------------+
> | foo |
> +------------+
>
> mSQL > select z1.string, z2.string from z1, z2 where z1.string = 'foo' and z2.string = 'foo' \g
> Query OK. 1 row(s) modified or retrieved.
> +------------+------------+
> | string | string |
> +------------+------------+
> | foo | foo |
> +------------+------------+
>
> mSQL > select z1.string, z2.string from z1, z2 where z1.string < 'fzz'\g
> Query OK. 1 row(s) modified or retrieved.
> +------------+------------+
> | string | string |
> +------------+------------+
> | foo | foo |
> +------------+------------+
>
> mSQL > select z1.string, z2.string from z1, z2 where z1.string < z2.string \g
> ERROR : MSQL server has gone away
>
> (msql2d reports: Forced server shutdown due to bad signal!)
>
>
>
> (restart daemon, msql, after patching...)
>
> Welcome to the miniSQL monitor. Type \h for help.
> mSQL > select z1.string, z2.string from z1, z2 where z1.string < z2.string \g
> Query OK. 0 row(s) modified or retrieved.
> +------------+------------+
> | string | string |
> +------------+------------+
> +------------+------------+
>
> mSQL > select z1.string, z2.string from z1, z2 where z1.string < z2.string \g
> ERROR : MSQL server has gone away
>
> (msql2d reports: Forced server shutdown due to bad signal!)
>
>
>
> Apparently it needed to hit it twice to get the crash.
>
> The first run was done with a unpatched 2.0B6 copy.
> The second run was done with after applying Robert N. Sum's
> "Wed, 16 Apr 97 09:53:30 -0400" patch, which may or may not have
> helped this problem.
>
>
>
> Machine:
>
> I'm working on a Linux box. (Red-Hat 4.0)
> % uname -a Linux discovery 2.0.18 #1 Tue Sep 10 10:15:48 EDT 1996 i686
>
> % bin/msqladmin version
>
> Version Details :-
>
> msqladmin version 2.0 Beta 6
> mSQL server version 2.0 Beta 6
> mSQL protocol version 22
> mSQL connection Localhost via UNIX socket
> Target platform Linux-2.0.18-i686
>
> Configuration Details :-
>
> Default config file /usr/local/mSQL/msql.conf
> TCP socket 3456
> UNIX socket /usr/local/mSQL/msql2.sock
> mSQL user dba
> Admin user dba
> Install directory /usr/local/mSQL
> PID file location /usr/local/mSQL/msql2d.pid
>
>
>
> Thanks for any help....
>
> -David Apfelbaum.
>
> --------------------------------------------------------------------------
> To remove yourself from the Mini SQL mailing list send a message containing
> "unsubscribe" to > "unsubscribe" to msql-list-request@bunyip.com. Send a message containing
> "info msql-list" to majordomo@bunyip.com for info on monthly archives of
> the list. For more help, mail owner-msql-list@bunyip.com NOT the msql-list!
>

--------------------------------------------------------------------------
To remove yourself from the Mini SQL mailing list send a message containing
"unsubscribe" to "unsubscribe" to msql-list-request@bunyip.com. Send a message containing
"info msql-list" to majordomo@bunyip.com for info on monthly archives of
the list. For more help, mail owner-msql-list@bunyip.com NOT the msql-list!