[support] Odd 'fatal error' but no problems in database and no changes to drupal files

[Chris Johnson]

Nick Holden wrote:
> On Monday 28 November 2005 22:09, Chris Johnson wrote:
> 
>>I think you are right that Drupal is sending a malformed query.  It appears
>>to be specifically the book.module that is generating it (or possibly a
>>contributed module).
> 
> 
> Why do you think it's the book module? I'm not even sure that we're using it!

It's just a guess based on the limited information available.  I searched all 
of the source code for core for SQL queries that match your error.  Only the 
book module has one like it.  That does not mean something else is not 
creating one bit by bit dynamically or that some contributed module is not 
doing it.  It was just my best guess.


> None of those URLs work - I get the same error message as on the home page 
> with all of them, which makes me think it's not a module that's messing up, 
> but something more core. But in that case why would it suddenly stop working?


Sorry they didn't work.  There was a chance that the bad SQl would not be run 
on admin pages and they would work if your session had not timed out.  No such 
luck.

I can only guess it stopped working because new content was added or something 
else in the database changed resulting in a bug getting exercised -- one that 
was avoided previously.  But again, I'm just guessing based upon the limited 
information and general experience with the software.

..chrisxj