Bug #414

1.4.6, pgsql, 'move thread' gives SQL error

Added by Nick Palmer about 1 year ago. Updated 8 months ago.

Status:Closed Start:08/20/2009
Priority:Normal Due date:
Assigned to:Tom Moore % Done:

100%
Category:Moderation
Target version:1.4.10
Reproducibility:Always Browser:
Reported In MyBB Version:1.4.8 Database Type:PostgreSQL
PHP Version: Database Version:8.3.7

Description

when I just tried to 'move thread', i got the following SQL error...

MyBB SQL Error

MyBB has experienced an internal SQL error and cannot continue.

    22P02 - ERROR: invalid input syntax for integer: "" 
Query:
    SELECT COUNT(p.pid) AS posts, u.uid FROM mybb_posts p LEFT JOIN mybb_users u ON (u.uid=p.uid) WHERE tid='' GROUP BY u.uid ORDER BY posts DESC

I selected the thread in the forum view, chose move threads, clicked Go(1), on the next screen selected the target forum (a new empty one), and hit Move Threads, and got that error.

using Postgres 8.3.7 on CentOS 5.3

Associated revisions

Revision 4445
Added by Tom Moore about 1 year ago

Fixes 1.4.6, pgsql, 'move thread' gives SQL error (fixes:414)

History

Updated by Tom Moore about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Applied in changeset r4445.

Updated by Tom Moore about 1 year ago

  • Assigned to set to Tom Moore
  • Target version set to 1.4.9
  • Database Type set to PostgreSQL
  • Database Version set to 8.3.7

Updated by Michael Schlechtinger about 1 year ago

  • Status changed from Resolved to Feedback

This fix is not working. Now you get another error message:

MyBB has experienced an internal SQL error and cannot continue.

SQL Error:
    42803 - ERROR: column "mybb_threads.lastpost" must appear in the GROUP BY clause or be used in an aggregate function 
Query:
    SELECT COUNT(tid) as threads FROM mybb_threads WHERE tid >= '1' AND fid = '2' AND lastpost >= '1251323264' AND (visible='1' OR visible='0') ORDER BY lastpost DESC

Updated by Ryan Gordon 12 months ago

  • Target version changed from 1.4.9 to 1.4.10

Updated by Tom Moore 10 months ago

  • Category set to Moderation
  • Status changed from Feedback to Resolved

Michael's error no longer applies; it was resolved in r4464 (I put the wrong fix number in the commit message).

Applied in changeset r4464.

Updated by Ryan Gordon 8 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF