Mariadb ошибка 1064 - Решение и исправление самых разных ошибок на TopOshibok.ru

When issuing a command to MySQL, I’m getting error #1064 «syntax error».

What does it mean?
How can I fix it?

asked May 7, 2014 at 10:32

TL;DR

Error #1064 means that MySQL can’t understand your command. To fix it:

Read the error message. It tells you exactly where in your command MySQL got confused.

Examine your command. If you use a programming language to create your command, use echo, console.log(), or its equivalent to show the entire command so you can see it.

Check the manual. By comparing against what MySQL expected at that point, the problem is often obvious.

Check for reserved words. If the error occurred on an object identifier, check that it isn’t a reserved word (and, if it is, ensure that it’s properly quoted).

Aaaagh!! What does #1064 mean?

Error messages may look like gobbledygook, but they’re (often) incredibly informative and provide sufficient detail to pinpoint what went wrong. By understanding exactly what MySQL is telling you, you can arm yourself to fix any problem of this sort in the future.

As in many programs, MySQL errors are coded according to the type of problem that occurred. Error #1064 is a syntax error.
- What is this «syntax» of which you speak? Is it witchcraft?
  
  Whilst «syntax» is a word that many programmers only encounter in the context of computers, it is in fact borrowed from wider linguistics. It refers to sentence structure: i.e. the rules of grammar; or, in other words, the rules that define what constitutes a valid sentence within the language.
  
  For example, the following English sentence contains a syntax error (because the indefinite article «a» must always precede a noun):
  
  This sentence contains syntax error a.
- What does that have to do with MySQL?
  
  Whenever one issues a command to a computer, one of the very first things that it must do is «parse» that command in order to make sense of it. A «syntax error» means that the parser is unable to understand what is being asked because it does not constitute a valid command within the language: in other words, the command violates the grammar of the programming language.
  
  It’s important to note that the computer must understand the command before it can do anything with it. Because there is a syntax error, MySQL has no idea what one is after and therefore gives up before it even looks at the database and therefore the schema or table contents are not relevant.
How do I fix it?

Obviously, one needs to determine how it is that the command violates MySQL’s grammar. This may sound pretty impenetrable, but MySQL is trying really hard to help us here. All we need to do is…
- Read the message!
  
  MySQL not only tells us exactly where the parser encountered the syntax error, but also makes a suggestion for fixing it. For example, consider the following SQL command:
```
UPDATE my_table WHERE id=101 SET name='foo'
```
  That command yields the following error message:
  
  ERROR 1064 (42000): 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 id=101 SET name='foo'' at line 1
  
  MySQL is telling us that everything seemed fine up to the word WHERE, but then a problem was encountered. In other words, it wasn’t expecting to encounter WHERE at that point.
  
  Messages that say ...near '' at line... simply mean that the end of command was encountered unexpectedly: that is, something else should appear before the command ends.
- Examine the actual text of your command!
  
  Programmers often create SQL commands using a programming language. For example a php program might have a (wrong) line like this:
```
$result = $mysqli->query("UPDATE " . $tablename ."SET name='foo' WHERE id=101");
```
  If you write this this in two lines
```
$query = "UPDATE " . $tablename ."SET name='foo' WHERE id=101"
$result = $mysqli->query($query);
```
  then you can add echo $query; or var_dump($query) to see that the query actually says
```
UPDATE userSET name='foo' WHERE id=101
```
  Often you’ll see your error immediately and be able to fix it.
- Obey orders!
  
  MySQL is also recommending that we «check the manual that corresponds to our MySQL version for the right syntax to use«. Let’s do that.
  
  I’m using MySQL v5.6, so I’ll turn to that version’s manual entry for an UPDATE command. The very first thing on the page is the command’s grammar (this is true for every command):
```
UPDATE [LOW_PRIORITY] [IGNORE] table_reference
    SET col_name1={expr1|DEFAULT} [, col_name2={expr2|DEFAULT}] ...
    [WHERE where_condition]
    [ORDER BY ...]
    [LIMIT row_count]
```
  The manual explains how to interpret this syntax under Typographical and Syntax Conventions, but for our purposes it’s enough to recognise that: clauses contained within square brackets [ and ] are optional; vertical bars | indicate alternatives; and ellipses ... denote either an omission for brevity, or that the preceding clause may be repeated.
  
  We already know that the parser believed everything in our command was okay prior to the WHERE keyword, or in other words up to and including the table reference. Looking at the grammar, we see that table_reference must be followed by the SET keyword: whereas in our command it was actually followed by the WHERE keyword. This explains why the parser reports that a problem was encountered at that point.
A note of reservation

Of course, this was a simple example. However, by following the two steps outlined above (i.e. observing exactly where in the command the parser found the grammar to be violated and comparing against the manual’s description of what was expected at that point), virtually every syntax error can be readily identified.

I say «virtually all», because there’s a small class of problems that aren’t quite so easy to spot—and that is where the parser believes that the language element encountered means one thing whereas you intend it to mean another. Take the following example:
```
UPDATE my_table SET where='foo'
```
Again, the parser does not expect to encounter WHERE at this point and so will raise a similar syntax error—but you hadn’t intended for that where to be an SQL keyword: you had intended for it to identify a column for updating! However, as documented under Schema Object Names:
If an identifier contains special characters or is a reserved word, you must quote it whenever you refer to it. (Exception: A reserved word that follows a period in a qualified name must be an identifier, so it need not be quoted.) Reserved words are listed at Section 9.3, “Keywords and Reserved Words”.
```
[ deletia ]
```
The identifier quote character is the backtick (“`”):
```
mysql> SELECT * FROM `select` WHERE `select`.id > 100;
```
If the ANSI_QUOTES SQL mode is enabled, it is also permissible to quote identifiers within double quotation marks:
```
mysql> CREATE TABLE "test" (col INT);
ERROR 1064: You have an error in your SQL syntax...
mysql> SET sql_mode='ANSI_QUOTES';
mysql> CREATE TABLE "test" (col INT);
Query OK, 0 rows affected (0.00 sec)
```

It is late but will help others and ofcourse will save time
My query was working in MySQL 5.7 in local system but on live we have version MySQL 8 and query stop working.

Query:

SELECT t.*
FROM groups t
ORDER BY t.id DESC
LIMIT 10 OFFSET 0

Output in MySQL 8:

Error in query (1064): Syntax error near ‘groups t ORDER BY t.id DESC’
at line …

I came to know groups is reserved word so I have to wrap groups with « quotes or change the table name to solve this issue.

answered Jul 18, 2021 at 13:13

Muhammad ShahzadMuhammad Shahzad

9,34821 gold badges86 silver badges130 bronze badges

For my case, I was trying to execute procedure code in MySQL, and due to some issue with server in which Server can’t figure out where to end the statement I was getting Error Code 1064. So I wrapped the procedure with custom DELIMITER and it worked fine.

For example, Before it was:

DROP PROCEDURE IF EXISTS getStats;
CREATE PROCEDURE `getStats` (param_id INT, param_offset INT, param_startDate datetime, param_endDate datetime)
BEGIN
    /*Procedure Code Here*/
END;

After putting DELIMITER it was like this:

DROP PROCEDURE IF EXISTS getStats;
DELIMITER $$
CREATE PROCEDURE `getStats` (param_id INT, param_offset INT, param_startDate datetime, param_endDate datetime)
BEGIN
    /*Procedure Code Here*/
END;
$$
DELIMITER ;

answered Apr 19, 2017 at 10:54

Umair MalhiUmair Malhi

5651 gold badge5 silver badges16 bronze badges

Источник

MariaDB is a powerful open-source relational database management system that is widely used in various applications. It is known for its stability, performance, and scalability, making it an ideal choice for data storage, management, and retrieval.

However, as with any complex software, there can be issues that arise when working with MariaDB. One common issue that users may encounter is the “MariaDB ERROR 1064” message.

In this MariaDB tutorial, we’ll explore the common causes of the ERROR 1064 message and provide tips on how to resolve it when trying to create a table, function, procedure, drop a database, and when using the “UPDATE” statement. We’ll also provide examples that demonstrate how to avoid errors and successfully complete the task.

This MariaDB tutorial is intended for developers, database administrators or anyone who is working with MariaDB and may encounter the ERROR 1064 message.

By understanding the causes of the ERROR 1064 message and following the tips provided in this MariaDB tutorial, you’ll be better equipped to troubleshoot and resolve the issue quickly, allowing you to continue your work without interruption.

MariaDB ERROR 1064
MariaDB ERROR 1064 Create User
How to solve the ERROR 1064 while Altering the User
How to deal with ERROR 1064 generated during Grant Privileges
What is MariaDB Insert ERROR 1064
How to resolve Create Table ERROR 1064
MariaDB Grant All Privileges ERROR 1064
How to solve Create Database ERROR 1064
MariaDB Create Procedure ERROR 1064
MariaDB Create Function ERROR 1064
How to solve Drop Database ERROR 1064
MariaDB Error 1064 in Update Set Statement

MariaDB Error 1064 is a syntax error that occurs when the MariaDB server is unable to parse a SQL statement. This error is usually caused by a typo or a missing component in the SQL statement.

Let’s see an example and understand how this kind of error appears.

SELECT * FROM users WHERE name = 'John' ANDD age > 35

MariaDB ERROR 1064

In this example, the AND keyword is misspelled as ANDD. When the MariaDB server tries to parse this statement, it will encounter an unexpected token and return MariaDB Error 1064.

To fix this error, you will need to examine the SQL statement and look for any typos or missing components. Once you have identified and corrected the problem, you should be able to execute the statement without encountering the error.

MariaDB ERROR 1064 Create User

MariaDB Error 1064 can occur when trying to create a user in MariaDB using the CREATE USER statement. A syntax error usually causes this error in the CREATE USER statement, such as a typo or a missing component.

Let’s take an example and see how the 1064 error occurs while creating the user.

CREATE USER 'john'@'localhost' IDENTIFIEDD BY 'password';

MariaDB ERROR 1064 Create User

In this example, the IDENTIFIED keyword is misspelled as IDENTIFIEDD. When the MariaDB server tries to parse this statement, it will encounter an unexpected token and return MariaDB Error 1064.

To fix this error, you will need to examine the CREATE USER statement and look for any typos or missing components. Once you have identified and corrected the problem, you should be able to execute the statement without encountering the error.

Also, check: How to Create Function in MariaDB

MariaDB ERROR 1064 Alter User

MariaDB Error 1064 can occur when you are trying to modify a user in MariaDB using the ALTER USER statement. A syntax error usually causes this error in the ALTER USER statement, such as a typo or a missing component.

Let’s take an example of an ALTER USER statement that would cause MariaDB Error 1064.

ALTER USER 'john'@'localhost' SET PASSWORD FOR 'password';

MariaDB ERROR 1064 Alter User

In this example, the FOR keyword is unnecessary and not allowed in the SET PASSWORD clause. When the MariaDB server tries to parse this statement, it will encounter an unexpected token and return MariaDB Error 1064.

To fix this error, you will need to examine the ALTER USER statement and look for any typos or unnecessary components. Once you have identified and corrected the problem, you should be able to execute the statement without encountering the error.

Read: How To Check MariaDB Version

MariaDB ERROR 1064 Grant Privileges

MariaDB Error 1064 can occur when you are trying to grant privileges to a user in MariaDB using the GRANT statement. A syntax error usually causes this error in the GRANT statement, such as a typo or a missing component.

Let’s see an example of a GRANT statement that would cause MariaDB Error 1064.

GRANT SELECT, INSERT, UPDATE, DELETE ON mydatabase. TO 'james'@'localhost';

MariaDB ERROR 1064 Grant Privileges

In this example, there is a syntax error in the GRANT statement after the database name. the MariaDB server will return MariaDB Error 1064.

To fix this error, you must ensure that the database specified in the GRANT statement exists and is spelled correctly. You may also need to check that the user specified in the TO clause exists and is spelled correctly.

GRANT SELECT, INSERT, UPDATE, DELETE ON mydatabase.* TO 'james'@'localhost';

Once you have identified and corrected the problem, you should be able to execute the GRANT statement without encountering the error.

Read: How to install MariaDB

MariaDB Insert ERROR 1064

MariaDB Error 1064 can occur when you are trying to insert data into a table in MariaDB using the INSERT statement. A syntax error usually causes this error in the INSERT statement, such as a typo or a missing component.

Let’s see with an example.

INSERT INTO users (id, name, age,country) VALUES (1, 'John', 30, 'USA')

In this example, there is no syntax error in the INSERT statement. However, if the users table does not have a column called id, the MariaDB server will return MariaDB Error 1064.

To fix this error, you will need to ensure that the column names specified in the INSERT statement match the columns in the table. You may also need to check that the values being inserted match the data types of the corresponding columns.

Once you have identified and corrected the problem, you should be able to execute the INSERT statement without encountering the error.

Read: MariaDB Vs SQL Server

MariaDB Create Table ERROR 1064

MariaDB Error 1064 can occur when trying to create a table in MariaDB using the CREATE TABLE statement. A syntax error usually causes this error in the CREATE TABLE statement, such as a typo or a missing component.

Let’s take an example of a CREATE TABLE a statement that would cause MariaDB Error 1064.

CREATE TABLE users (id INT PRIMARY KEY, name VARCHAR(255) NOT NULL, age INT NOT NULL);

In this example, there is no syntax error in the CREATE TABLE statement. However, if the user’s table already exists, the MariaDB server will return MariaDB Error 1064.

To fix this error, you will need to ensure that the table does not already exist, or specify the IF NOT EXISTS clause to indicate that the table should be created only if it does not already exist.

Once you have identified and corrected the problem, you should be able to execute the CREATE TABLE statement without encountering the error.

Read MariaDB Timestamp

MariaDB Create Procedure ERROR 1064

MariaDB Error 1064 can occur when trying to create a stored procedure in MariaDB using the CREATE PROCEDURE statement. A syntax error usually causes this error in the CREATE PROCEDURE statement, such as a typo or a missing component.

Let’s take an example of a CREATE PROCEDURE statement that would cause MariaDB Error 1064.

CREATE PROCEDURE get_users()
BEGIN
SELECT * FROM users;
END

MariaDB Create Procedure ERROR 1064

In this example, there is no syntax error in the CREATE PROCEDURE statement, however, if the users table does not exist, the MariaDB server will return MariaDB Error 1064.

To fix this error, you must ensure that the table specified in the SELECT statement exists and is spelled correctly. Also, you may need to check for any missing or incorrect syntax used in the procedure.

Once you have identified and corrected the problem, you should be able to execute the CREATE PROCEDURE statement without encountering the error.

MariaDB Create Function ERROR 1064

MariaDB Error 1064 can occur when trying to create a stored function in MariaDB using the CREATE FUNCTION statement. A syntax error usually causes this error in the CREATE FUNCTION statement, such as a typo or a missing component.

CREATE FUNCTION get_user_count()
RETURNS INT
BEGIN
   RETURN (SELECT COUNT(*) FROM users);
END

MariaDB Create Function ERROR 1064

In the above example, the “ERROR 1064” message is generated by MariaDB when it encounters a syntax error in the SQL statement used to create the function.

This error message can be caused by a number of issues, such as using reserved keywords as a function or variable names, including special characters in function or variable names, using incorrect syntax when defining function parameters, or using invalid data types for function parameters or variables.

MariaDB Drop Database ERROR 1064

Dropping a database in MariaDB is a common task that can be accomplished using the “DROP DATABASE” statement. However, in some cases, you may encounter the “ERROR 1064” message when trying to drop a database. This error message is generated when MariaDB encounters a syntax error in the SQL statement used to drop the database.

A common reason for this error message is if you’re trying to drop a database that does not exist. For example, if you try to drop a database named “mydb” but there is no database with that name on the MariaDB server, you will receive an ERROR 1064 message.
To avoid this, you should ensure that the database you’re trying to drop actually exists by running a “SHOW DATABASES” command to list all the databases on the server.
Another common cause of the ERROR 1064 message is the use of invalid characters in the database name. In MariaDB, database names can only contain letters, numbers, and the underscore character.
If you try to drop a database with a name that contains invalid characters, such as a dash or a space, you will receive an ERROR 1064 message.

In some cases, you may also receive an ERROR 1064 message if the database you’re trying to drop is currently in use. If a user is connected to the database or if there are active queries running on the database, you will not be able to drop it.

MariaDB Drop Database ERROR 1064

In the above example, “mydb” is the name of the database you want to drop. Once you run this command, It will show an error because the keyword DATABASE is mentioned as DATABAS which is the wrong syntax.

To avoid the ERROR 1064 message when trying to drop a database in MariaDB, you should ensure that the database you’re trying to drop actually exists, that the name of the database is correct and doesn’t contain invalid characters, also ensure that the database isn’t currently in use.

MariaDB Error 1064 in Update Set Statement

The “ERROR 1064” message can also occur when using the “UPDATE” statement in MariaDB. One common cause of this error when using the “UPDATE” statement is a syntax error in the “SET” clause.

The “SET” clause is used to specify the new values for the columns that are being updated. If there is a syntax error in this clause, MariaDB will return an “ERROR 1064” message.

For example, if you try to update a column named “price” with the value “20.5” in the “products” table, but you forget to include the column name in the “SET” clause, like this.

UPDATE products SET 20.5 WHERE id = 1;

MariaDB Error 1064 in Update Set Statement

You will receive an “ERROR 1064” message, because the statement is missing the column name before the value. The correct syntax should be.

UPDATE products SET price = 20.5 WHERE id = 1;

Another common cause of the “ERROR 1064” message when using the “UPDATE” statement is using the wrong data type for a column value. For example, if you try to update an integer column with a string value, you will receive an “ERROR 1064” message. To avoid this, you should check the data types of the columns that you are updating and ensure that the values you are using match the correct data types.

Additionally, using reserved keywords as column names can cause an ERROR 1064, also using invalid characters as column names would cause an error as well.

To resolve this error, you should carefully review the “UPDATE” statement and check for any syntax errors in the “SET” clause. Make sure that you include the column name before the value and ensure that the data types match. Also, ensure that the column names are not reserved keywords and don’t have any invalid characters.

You may like the following MariaDB tutorials:

How to Add Column in MariaDB
MariaDB Create Temporary Table From Select

Conclusion

In this MariaDB tutorial, we’ve provided examples and tips on resolving the ERROR 1064 message when creating a function, dropping a database, and using the “UPDATE” statement. By understanding the causes of the error and following the tips provided, you can avoid the ERROR 1064 message and work effectively with MariaDB.

It’s always a good idea to keep the MariaDB documentation on hand, as well as search online for troubleshooting guides or forums dedicated to MariaDB where you can find solutions to common problems and seek help from more experienced users.

The key takeaway is that MariaDB is a robust and reliable database system, but like any other software, it may have some issues. With a proper understanding of the syntax, reserved keywords, and data types, you can avoid such issues and maintain the smooth functioning of your databases.

MariaDB ERROR 1064
MariaDB ERROR 1064 Create User
How to solve the ERROR 1064 while Altering the User
How to deal with ERROR 1064 generated during Grant Privileges
What is MariaDB Insert ERROR 1064
How to resolve Create Table ERROR 1064
MariaDB Grant All Privileges ERROR 1064
How to solve Create Database ERROR 1064
MariaDB Create Procedure ERROR 1064
MariaDB Create Function ERROR 1064
How to solve Drop Database ERROR 1064
MariaDB Error 1064 in Update Set Statement

Bijay

I am Bijay having more than 15 years of experience in the Software Industry. During this time, I have worked on MariaDB and used it in a lot of projects. Most of our readers are from the United States, Canada, United Kingdom, Australia, New Zealand, etc.

Want to learn MariaDB? Check out all the articles and tutorials that I wrote on MariaDB. Also, I am a Microsoft MVP.

Источник

I was trying to run following Query on my sql server :

CREATE TABLE `e_store`.`products`(
    `id` INT UNSIGNED NOT NULL AUTO_INCREMENT ,
    `name` VARCHAR(250) NOT NULL ,
    `brand_id` INT UNSIGNED NOT NULL ,
    `category_id` INT UNSIGNED NOT NULL ,
    `attributes` JSON NOT NULL ,
    PRIMARY KEY(`id`) ,
    INDEX `CATEGORY_ID`(`category_id` ASC) ,
    INDEX `BRAND_ID`(`brand_id` ASC) ,
    CONSTRAINT `brand_id` FOREIGN KEY(`brand_id`) REFERENCES `e_store`.`brands`(`id`) ON DELETE RESTRICT ON UPDATE CASCADE ,
    CONSTRAINT `category_id` FOREIGN KEY(`category_id`) REFERENCES `e_store`.`categories`(`id`) ON DELETE RESTRICT ON UPDATE CASCADE
);

I have already brands and categories tables on my e_store database.

But I got the following Error :

#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'JSON NOT NULL ,
    PRIMARY KEY(`id`) ,
    INDEX `CATEGORY_ID`('category_id' ' at line 6

Источник

So, you’re creating a custom SQL query to perform a task in the database. After putting the code together and running it in PHPmyAdmin it responds with a 1064 error. It may look similar to this:

The 1064 error displays any time you have an issue with your SQL syntax, and is often due to using reserved words, missing data in the database, or mistyped/obsolete commands. So follow along and learn more about what the 1064 error is, some likely causes, and general troubleshooting steps.

Note: Since syntax errors can be hard to locate in long queries, the following online tools can often save time by checking your code and locating issues:

PiliApp MySQL Syntax Check
EverSQL SQL Query Syntax Check & Validator

Causes for the 1064 error

Reserved Words
Missing Data
Mistyped Commands
Obsolete Commands

This may seem cryptic since it is a general error pointing to a syntax issue in the SQL Query statement. Since the 1064 error can have multiple causes, we will go over the most common things that will result in this error and show you how to fix them. Follow along so you can get your SQL queries updated and running successfully.

Using Reserved Words

Every version of MySQL has its own list of reserved words. These are words that are used for specific purposes or to perform specific functions within the MySQL engine. If you attempt to use one of these reserved words, you will receive the 1064 error. For example, below is a short SQL query that uses a reserved word as a table name.

CREATE TABLE alter (first_day DATE, last_day DATE);

How to fix it:

Just because the word alter is reserved does not mean it cannot be used, it just has special requirements to use it as the MySQL engine is trying to call the functionality for the alter command. To fix the issue, you will want to surround the word with backticks, this is usually the button just to the left of the “1” button on the keyboard. The code block below shows how the code will need to look in order to run properly.

CREATE TABLE `alter` (first_day DATE, last_day DATE);

Missing Data

Sometimes data can be missing from the database. This causes issues when the data is required for a query to complete. For example, if a database is built requiring an ID number for every student, it is reasonable to assume a query will be built to pull a student record by that ID number. Such a query would look like this:

SELECT * from students WHERE studentID = $id

If the $id is never properly filled in the code, the query would look like this to the server:

SELECT * from students WHERE studentID =

Since there is nothing there, the MySQL engine gets confused and complains via a 1064 error.

How to fix it:

Hopefully, your application will have some sort of interface that will allow you to bring up the particular record and add the missing data. This is tricky because if the missing data is the unique identifier, it will likely need that information to bring it up, thus resulting in the same error. You can also go into the database (typically within phpMyAdmin) where you can select the particular row from the appropriate table and manually add the data.

Mistyping of Commands

One of the most common causes for the 1064 error is when a SQL statement uses a mistyped command. This is very easy to do and is easily missed when troubleshooting at first. Our example shows an UPDATE command that is accidentally misspelled.

UDPATE table1 SET id = 0;

How to fix it:

Be sure to check your commands prior to running them and ensure they are all spelled correctly.

Below is the syntax for the correct query statement.

UPDATE table1 SET id = 0;

Obsolete Commands

Some commands that were deprecated (slated for removal but still allowed for a period of time) eventually go obsolete. This means that the command is no longer valid in the SQL statement. One of the more common commands is the ‘TYPE‘ command. This has been deprecated since MySQL 4.1 but was finally removed as of version 5.1, where it now gives a syntax error. The ‘TYPE‘ command has been replaced with the ‘ENGINE‘ command. Below is an example of the old version:

CREATE TABLE t (i INT) TYPE = INNODB;

This should be replaced with the new command as below:

CREATE TABLE t (i INT) ENGINE = INNODB;

For developers or sysadmins experienced with the command line, get high availability and root access for your application, service, and websites with Cloud VPS Hosting.

Error 1064 Summary

As you can see there is more than one cause for the 1064 error within MySQL code. Now, you know how to correct the issues with your SQL Syntax, so your query can run successfully. This list will be updated as more specific instances are reported.

Источник

Resolving the MariaDB error 1064 error quickly can save the site from downtime and increase website stability. Our experts are here to answer queries like these as a part of our MySQL Support Services.

What Causes MariaDB Error 1064?

The MariaDB error 1064 happens when there is an error in the syntax of the command. This usually occurs when we make a mistake while typing a command and MySQL can’t understand the command. Obsolete or Outdated commands can also lead to MariaDB error 1064.

In this article, our Support team point out some of the reason for the error and then put forward the solution for each cause. Let’s examine each cause one by one.

Missing Data

When a query needs data from the database so that it can complete and can’t locate the data, then we may see MariaDB error 1064.

Solution:
We can access the database through phpMyAdmin, choose the specific row from the relevant table which miss the data, and then manually fill in the missing data.

Wrongly Typed Commands

When a SQL statement employs an incorrect command, it is one of the most frequent causes of the 1064 error.

Solution:
Confirm the typed commands are correct. We have to manually check and make sure all the commands are correctly typed before running it.

Obsolete Commands

New commands will replace the older ones over time. These commands are slated for removal but are still allowed for a period of time. However, these commands in not valid in the SQL statements and gives a syntax error. This will in turn display the MariaDB error 1064.

Solution:
The relevant sections of the MySQL Reference Manual will list any obsolete commands. We simply use the “find and replace” function to get rid of the outdated command and insert the new one after identifying it.

Reserved Words

In MySQL, if we use a reserved word out of context, it will be interpreted incorrectly and cause a syntax error. This results in error 1064.

Solution:
Some commands have special requirements to use it as the MySQL engine is trying to call the functionality for the command. We can read up on it in the MySQL Reference Manual. So a quick find and replace should enable us to resolve this issue if we think it may be causing the MariaDB error 1064.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To sum up, our Support team went over the MariaDB error 1064 details.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Источник

TL;DR

Aaaagh!! What does #1064 mean?

What is this «syntax» of which you speak? Is it witchcraft?

What does that have to do with MySQL?

How do I fix it?

Read the message!

Examine the actual text of your command!

Obey orders!

A note of reservation

MariaDB ERROR 1064 Create User

MariaDB ERROR 1064 Alter User

MariaDB ERROR 1064 Grant Privileges

MariaDB Insert ERROR 1064

MariaDB Create Table ERROR 1064

MariaDB Create Procedure ERROR 1064

MariaDB Create Function ERROR 1064

MariaDB Drop Database ERROR 1064

MariaDB Error 1064 in Update Set Statement

Conclusion

Causes for the 1064 error

Using Reserved Words

Missing Data

Mistyping of Commands

Obsolete Commands

Error 1064 Summary

What Causes MariaDB Error 1064?

Missing Data

Wrongly Typed Commands

Obsolete Commands

Reserved Words

Conclusion

PREVENT YOUR SERVER FROM CRASHING!