Back to the month index |
Back to the list index
|
John Fulmer (jfulmer@iegroup.com)
Tue, 31 Dec 1996 10:16:11 -0600
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Jesper Weissglas: "[mSQL] 2.0B1 Problems with character case in LIKE"
- Previous message: John Fulmer: "[mSQL] Msql 2.0 bug (solved)"
Message-Id: <32C93C4B.3F9427C7@iegroup.com> Date: Tue, 31 Dec 1996 10:16:11 -0600 From: John Fulmer <jfulmer@iegroup.com> Subject: [mSQL] Another MSQL buggieI found another bug, apparently related to the one I found before in
msql 2.0 B1.
Somehow, I don't know how, a NULL was inserted into my INDEX field on a
row (which is an INT, btw). Now, whenever I try to use w3-msql, it hangs
on the pages. Also, when using the msql monitor, if I try to delete the
row, it get the following message:
mSQL > DELETE from support_info
-> WHERE company_id = NULL
-> \g
ERROR : Index condition for "company_id" cannot be NULL
Now, I know that it is not correct for an index to be NULL, but
shouldn't msql complain instead of accepting the NULL?
jf
-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + John Fulmer | "UNIX was not designed to stop + + Secure Network System | you from doing stupid things, + + Lawrence, Kansas | because that would also stop you + + | from doing clever things." + + jfulmer@iegroup.com | + + http://www.iegroup.com | -- Larry Wall + + + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -------------------------------------------------------------------------- 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!
- Next message: Jesper Weissglas: "[mSQL] 2.0B1 Problems with character case in LIKE"
- Previous message: John Fulmer: "[mSQL] Msql 2.0 bug (solved)"