Bug 137318 - Changing password causes SQL error
Changing password causes SQL error
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
All Linux
medium Severity medium (vote)
: ---
: ---
Assigned To: Mike MacKenzie
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-10-27 11:07 EDT by David Lawrence
Modified: 2007-04-18 13:14 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-27 17:21:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Lawrence 2004-10-27 11:07:05 EDT
Description of problem:
Main page
logged out
Log in screen
Enter rperkins@redhat.com in box
Click Submit Request

-- Software error:

DBD::Pg::st execute failed: ERROR:  parser: parse error at or near "10" at
character 271 [for Statement "SELECT profiles.userid, tokens.issuedate FROM profiles
                    LEFT JOIN tokens
                    ON tokens.userid = profiles.userid
                    AND tokens.tokentype = 'password'
                    AND tokens.issuedate > DATE_SUB(NOW(), INTERVAL 10 MINUTE)
                    WHERE login_name = 'rperkins@redhat.com'"] at Bugzilla/DB.pm
line 74
    Bugzilla::DB::SendSQL('SELECT profiles.userid, tokens.issuedate FROM
profiles \x{a}     ...') called at Bugzilla/Token.pm line 119
    Bugzilla::Token::IssuePasswordToken('rperkins@redhat.com') called at
/var/www/bugzilla/beta2/token.cgi line 160
    main::requestChangePassword() called at /var/www/bugzilla/beta2/token.cgi
line 133

Version-Release number of selected component (if applicable):
2.18 beta2

Additional Info:
Is SQL compatibility problem with date arithmetic. PostgreSQL and MySQL are
Comment 1 Mike MacKenzie 2004-10-27 17:21:46 EDT
This is now fixed.  It should show up in the next beta of 2.18.

Note You need to log in before you can comment on or make changes to this bug.