mysql> INSERT INTO helps_needed values('Xantha','test');
Query OK, 1 row affected (0.00 sec)
Like I said it's a valid query. The mud actually WRITES the query just
fine, sends it to the database, the database responds to the query
perfectly. All of this is happening before crash_copyover. This is why
(originally) I had thought it was a signal handling issue, but shouldn't
that affect even reading from the db??
+----------------------------------------------------+
+ TJW: Head Tech, designer: Dreamless Realms Mud +
+ Mud : http://drealms.kyndig.com +
+ Telnet: drealms.kyndig.com port 9275 +
+ OLC Docs: http://olc.kyndig.com +
+----------------------------------------------------+
-----Original Message-----
From: Jason Gauthier [mailto:[EMAIL PROTECTED]
Sent: Monday, June 10, 2002 12:50 PM
To: '[EMAIL PROTECTED]'; '[email protected]'
Subject: RE: Advanced (kinda): Mysql & connection problems
Connect to the mysql database outside of the mud using the username and
password the mud connects as:
mysql <database> <user> -p
<enter password>
Execute the same query here in the mysql interface:
INSERT INTO helps_needed values('Xantha','test');
And see what happens.
>Cause: Unknown
>Error: (error length: 0)
>executing: INSERT INTO helps_needed VALUES ('Xantha','test') (It IS a
>valid query)
> (In this case, it's not really helpful, though usually, yeah I'd agree
>it is:))
>--
>the define for &my_connection:
>MYSQL my_connection;
>
>
>
>
