#Phpstorm mysql manual

#Phpstorm mysql manual

MariaDB > select * from settings where key like ' %primary_color% ' ERROR 1064 ( 42000 ) : 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 ' key like ' %primary_color% '' at line 1 To achieve that we can run the query bellow, which blows up, because it doesn't know what ' key' is. Now let's suppose we want to retrieve the data in our settings table filtering by some specific key. However, we use that same word for commands like ALTER TABLE tbl_name DROP FOREIGN KEY fk_symbol. Notice that we are using a column named ' key' and that's fine, our Database Management System (DBMS) did not complain about it. In our scenario we have the settings database described as follows: MariaDB > describe settings +-+-+-+-+-+-+ | Field | Type | Null | Key | Default | Extra | +-+-+-+-+-+-+ | id | int ( 10 ) unsigned | NO | PRI | NULL | auto_increment | | key | varchar ( 191 ) | NO | UNI | NULL | | | value | longtext | YES | | NULL | | | description | varchar ( 191 ) | YES | | NULL | | +-+-+-+-+-+-+ 6 rows in set ( 0.04 sec ) The problem when querying column names with reservedВ words Although it's fine to name columns whatever you like, there is one small issue when writing raw SQL queries against the database when you do use reserved words as column names. In this article we are going to setup a kind of 'typo checker' on PhpStorm to look for MySQL reserved words being used as column names in your Laravel migration files.