* lang/*:
- New variables for SQL Parser error messages
This commit is contained in:
@@ -420,4 +420,13 @@ $strValidateSQL = 'Validate SQL'; //to translate
|
||||
$strNoExplain = 'Skip Explain SQL'; //to translate
|
||||
$strExplain = 'Explain SQL'; //to translate
|
||||
$strCharsetOfFile = 'Character set of the file:'; //to translate
|
||||
$strBeginCut = 'BEGIN CUT'; //to translate
|
||||
$strEndCut = 'END CUT'; //to translate
|
||||
$strSQPBugInvalidIdentifer = 'Invalid Identifer'; //to translate
|
||||
$strSQPBugUnknownPunctation = 'Unknown Punctation String'; //to translate
|
||||
$strSQPBugUnclosedQuote = 'Unclosed quote'; //to translate
|
||||
$strBeginRaw = 'BEGIN RAW'; //to translate
|
||||
$strEndRaw = 'END RAW'; //to translate
|
||||
$strSQLParserBugMessage = 'There is a change that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if my parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:'; //to translate
|
||||
$strSQLParserUserError = 'There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem'; //to translate
|
||||
?>
|
||||
|
Reference in New Issue
Block a user