Just saw this error email for one of my forums.

Discussion in 'Bugs Report and Tracking' started by robdog, Jul 30, 2009.

  1. robdog New Member

    Not sure if this is the right place to post this, please move it if it is in the wrong place.

    Thanks.
  2. winter Tapatalk Master

    We are trying to reproduce it but so far no luck, if you know a way please let us know!
  3. stardotstar New Member

    I know this thread is waaay old but I am getting this a lot but only from one user who I have contacted to see if I can get platform and version details from.

    I googled the error and came only on this one thread of relevance from 2009.

    My board is vBulletin 3.8.4 Patch Level 2.

    My tapatalk module is latest I am pretty sure.

    Here is one of the errors (always same user)

    Code:
    atabase error in vBulletin 3.8.4:
    
    Invalid SQL:
    
    			SELECT post.postid
    			FROM post AS post
    			
    			WHERE post.threadid = 118667
    				AND post.visible = 1
    				AND post.userid NOT IN (33226)
    				
    			ORDER BY post.dateline 
                                    LIMIT 0, -10;
    
    MySQL Error   : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '-10' at line 9
    Error Number  : 1064
    Request Date  : Tuesday, April 5th 2011 @ 05:14:56 AM
    Error Date    : Tuesday, April 5th 2011 @ 05:14:56 AM
    Script        : http://www.archeli.com.au/forums/mobiquo/mobiquo.php
    Referrer      : 
    IP Address    : 124.169.176.123
    Username      : satchY
    Classname     : vB_Database
    MySQL Version :
    
    it repeats many times before (I guess) the member gives up.
  4. stardotstar New Member

    Apparently this is an android user.
    Are there no other reports of this?
  5. Yao Android Developer

    It seems something wrong when the app generate the pagination counter. We have added some check in the latest android version to make sure it does not land on a invalid page.

    The issue should not appear anymore if your user updated the app.

Share This Page