From: Len Hatfield <lhat@uo...> - 2012-04-02 22:41:16
I'm finding that our several years' old installation of refbase 0.9.5, running on php 5.2.15 has started spitting out MySQL errors when I try to import new records or even edit existing records. The editing process itself also fails, while the import process seems to succeed in that selected records all find their way into the RefBase.refs table, even though the system returns the following MySQL error message:
SELECT author, title, type, year, publication, abbrev_journal, volume, issue, pages, keywords, abstract, thesis, editor, publisher, place, abbrev_series_title, series_title, series_editor, series_volume, series_issue, edition, language, author_count, online_publication, online_citation, doi, serial, marked, copy, selected, user_keys, user_notes, user_file, user_groups, cite_key, related, orig_record, serial, file, url, doi, isbn, type FROM refs LEFT JOIN user_data ON serial = record_id AND user_id = WHERE serial RLIKE "^(1449)$" ORDER BY first_author, author_count, author, year, title
caused the following error:
Error 1064: 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 'WHERE serial RLIKE "^(1449' at line 1
I find this pretty confusing since as far as I can see, I issued no such 'SELECT' command--though perhaps this is appended in processing the edit or inserting a new record.
I wasn't able to find anything specifically on this in the RefBase forum, so I thought I'd see if the wider community might have encountered similar oddments or might have suggestions about where I might usefully look further.
From: Len Hatfield <lhat@uo...> - 2012-04-03 23:22:59
well, some things have changed over the years--individual tweaks and a few updates from svn--but I received this MySQL error message when I ran the command-line version of the import script (so that's why it lacks a user-id number, I'll bet): in short, it doesn't seem to be browser dependent.
Research Database @ CTL
On Apr 2, 2012, at 5:00PM, Richard Karnesky wrote:
So has anything changed in your installation?
That query has no user_id #. Have you tried logging in again? Have
you tried it from another browser?
From: Rick Karnesky <karnesky@gm...> - 2012-04-04 00:08:02
> but I received this MySQL error message when I ran the command-line version of the import script (so that's why it lacks a user-id number, I'll bet):
I doubt it: when a query is made from the command line client, the
server sues the user_id corresponding to the user/pass combo that you
use. Can you share other SQL errors? Do they all lack a user_id?
It will also be hard to troubleshoot this without knowing what tweaks
have been made. They might be to blame here: we don't see such a bug
in the stock 0.9.5 and, as you mentioned, I don't think we've seen
others report anything similar.
You can install a stock copy of refbase-0.9.5 in a separate directory on
the server, but tell it to use the same database as your currently
deployed version. That might at least narrow it down to either a
problem with those tweaks or something else.