On 27-Apr-2004 zzapper wrote:
> On Tue, 27 Apr 2004 22:26:16 +0100, wrote:
>
>>I only use mysql with php so all I need is
>>
>>php code:
>>$result = mysql_query($sql) or die(mysql_error());
>>
>>This always tells me what I did wrong in the query. You could easily
>>put
>>together a very short script into which you just drop you query. THis
>>would output the problem to the page. Dead simple and quick.
>>
>>Rich
>>
>>Joshua J. Kugler wrote:
>>
>>> On Tuesday 27 April 2004 04:26 am, zzapper said something like:
>>>
>>>>Even though I solved the following problem myself, I'd like to know
>>>>what debugging strategy people use to solve problems when they get
>>>>the
>>>>dreaded "Error in Mysql look in the manual"
>>>
>>>
>>> Fire up MySQL CC and paste the SQL in there, and see what error it
>>> gives me.
>>> As in 'You have an error near....' type messages.
>>>
>>> j----- k-----
>>>
> When I've got a horrible query with joins etc, I don't find the "your
> error near .." very useful or am I giving up to easy?
Howzabout :
mysql_query($qry) or
die(sprintf('<p>Borked query at file %s line %d :<br />%s',
__FILE__, __LINE__, nl2br($qry)) .'<br />'
.mysql_errno() .'<br />' .mysql_error());
--
Don Read [EMAIL PROTECTED]
-- It's always darkest before the dawn. So if you are going to
steal the neighbor's newspaper, that's the time to do it.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
