That’s my point, as is typical these days the error message is quoting back the statement with a rough indication of where the syntactical problem occurs, the problem being that the syntax quoted back in the error message (which is syntactically incorrect) is not the one passed to selectrow_array(), i.e. the original SQL reads “where epoch” but the error being generated by the db engine appears to have received a statement which instead reads “and epoch”...