There may be a few reasons why MariaDB produces an error for a subquery's unknown column while MySQL does not:
MariaDB is stricter when it comes to SQL standards and syntax. It might be possible that the query that runs on MySQL is not actually valid SQL and MariaDB is simply following the standard more closely.
MariaDB could have different default settings than MySQL. For example, the SQL mode in MariaDB may be configured to be stricter than MySQL, which would cause certain queries to fail.
The version of MariaDB being used may have changed since the last time the query was executed on MySQL. It's possible that the newer version of MariaDB has different behavior or requirements than the version of MySQL that was used previously.
Overall, while MariaDB and MySQL are very similar database management systems, there may be some subtle differences in behavior that could cause one to produce an error while the other does not.
Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss
Asked: 2023-06-05 16:32:16 +0000
Seen: 15 times
Last updated: Jun 05 '23
What is the method for placing parentheses in column names when creating a table using an SQL query?
What are the different technology combinations available for LAMP stack?
What causes an error in SQLAlchemy and MariaDB when using a column named 'row_number'?
How can I use bash to select rows from a table by referencing another table?
What is the issue encountered when attempting to use Spring Batch with MariaDB?
How can I install MariaDB and MySQL on my MacBook Pro?
How can I establish a connection with MariaDB that is running in a Docker container through dbeaver?
How can a "where in" query be executed using the MariaDB Python Connector?