docs: error code PG error 42P01 | MySQL error 1064 | MySQL error 1146 (#1048)

* add error code

* update

* update

* rm time

Author: adela-bytebase

content/reference/mysql/error/1064-syntax-error.md

@@ -0,0 +1,96 @@
+---
+title: 'ERROR 1064 (42000): You Have an Error in Your SQL Syntax'
+---
+
+## Error Message
+
+```sql
+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 '...' at line N
+```
+
+## Description
+
+MySQL error 1064 means the parser could not understand your SQL statement. The `near '...'` portion of the message shows where MySQL gave up trying to parse. Everything before that point was accepted; the error starts at (or just before) the quoted text.
+
+This is the single most common MySQL error. It covers everything from a missing comma to using a reserved word as a column name.
+
+## Causes
+
+- **Typos in SQL keywords.** `SELCET`, `UDPATE`, `FORM` instead of `SELECT`, `UPDATE`, `FROM`.
+- **Missing or extra punctuation.** Unmatched parentheses, missing commas between column definitions, trailing commas before a closing parenthesis.
+- **Using a reserved word as an identifier.** Column or table names like `order`, `group`, `key`, `status`, `rank`, `index` conflict with MySQL keywords.
+- **Version mismatch.** Syntax valid in MySQL 8.0 (like `LATERAL`, window functions, or `WITH` CTEs) fails on MySQL 5.7.
+- **Importing a dump from a different engine.** A PostgreSQL or SQL Server dump contains syntax MySQL does not recognize.
+- **Wrong string quoting.** Using double quotes for strings instead of single quotes (unless `ANSI_QUOTES` SQL mode is enabled).
+- **Invisible characters.** Copy-pasting SQL from a web page or PDF can introduce non-breaking spaces or zero-width characters that look fine but break parsing.
+
+## Solutions
+
+1. **Read the error message carefully.** MySQL tells you exactly where parsing failed. The text after `near` is the first thing it couldn't parse:
+
+   ```sql
+   -- Error: ... near 'FROM users WHERE id = 1' at line 1
+   -- The problem is right before FROM — likely a missing column name or comma
+   ```
+
+2. **Escape reserved words with backticks:**
+
+   ```sql
+   -- Fails: order is a reserved word
+   SELECT * FROM order WHERE id = 1;
+
+   -- Works
+   SELECT * FROM `order` WHERE id = 1;
+   ```
+
+3. **Check for missing commas and parentheses:**
+
+   ```sql
+   -- Fails: missing comma between columns
+   CREATE TABLE users (
+     id INT PRIMARY KEY
+     name VARCHAR(100)    -- missing comma on previous line
+   );
+
+   -- Works
+   CREATE TABLE users (
+     id INT PRIMARY KEY,
+     name VARCHAR(100)
+   );
+   ```
+
+4. **Remove trailing commas:**
+
+   ```sql
+   -- Fails: trailing comma before closing parenthesis
+   INSERT INTO users (name, email,) VALUES ('Alice', 'alice@example.com');
+
+   -- Works
+   INSERT INTO users (name, email) VALUES ('Alice', 'alice@example.com');
+   ```
+
+5. **Check your MySQL version:**
+
+   ```sql
+   SELECT VERSION();
+   ```
+
+   If you're using MySQL 5.7 and the query uses 8.0+ syntax (CTEs, window functions, `GROUPING`), rewrite it or upgrade.
+
+6. **Strip invisible characters.** Re-type the query manually in your SQL client rather than pasting from a browser or document.
+
+## Common scenarios
+
+**WordPress and CMS database imports:** Importing a `.sql` dump into a different MySQL version often triggers 1064 on statements like `CREATE TABLE` that use newer column types or options. Check the MySQL version at the source and target.
+
+**ORM-generated queries:** When an ORM builds SQL that references a reserved word as a column name without backticks, you get 1064. Most ORMs have a setting to force-quote identifiers.
+
+**Stored procedures and triggers:** Syntax errors inside `BEGIN...END` blocks are harder to spot. Simplify the procedure to the minimum and add statements back one at a time.
+
+<HintBlock type="info">
+
+Bytebase's [SQL Review](https://www.bytebase.com/docs/sql-review/review-rules/) checks SQL syntax and common mistakes before changes reach your database. You can configure rules for [MySQL naming conventions](/reference/mysql/how-to/top-mysql-commands-with-examples/) and reserved word usage.
+
+</HintBlock>

content/reference/mysql/error/1146-table-doesnt-exist.md

@@ -0,0 +1,109 @@
+---
+title: "ERROR 1146 (42S02): Table Doesn't Exist"
+---
+
+## Error Message
+
+```sql
+ERROR 1146 (42S02): Table 'mydb.users' doesn't exist
+```
+
+## Description
+
+MySQL error 1146 means the query references a table that MySQL cannot find in the specified database. The error message includes the fully qualified name (`database.table`) so you can see exactly which table and database MySQL looked in.
+
+## Causes
+
+- **Typo in the table name.** `SELECT * FROM uesrs` fails when the table is `users`.
+- **Wrong database.** The table exists in `production` but the connection is to `staging`. MySQL only sees tables in the currently selected database (or explicitly qualified ones).
+- **Table was dropped or never created.** A migration failed, a manual `DROP TABLE` happened, or the CREATE statement was never run.
+- **Case sensitivity on Linux.** MySQL table names map to files on disk. On Linux (case-sensitive filesystem), `Users` and `users` are different tables. On macOS and Windows, they're the same.
+- **InnoDB data dictionary mismatch.** The `.frm` file (MySQL 5.7 and earlier) or the InnoDB data dictionary (MySQL 8.0+) is out of sync with the actual tablespace files. This happens after a crash, incomplete restore, or manual file manipulation.
+- **Corrupted table.** Improper server shutdown, disk failure, or interrupted operations can corrupt table metadata.
+- **Missing privileges.** If the user has no privileges on the table at all, MySQL may report it as not existing rather than access denied (depending on configuration).
+
+## Solutions
+
+1. **Verify the table exists:**
+
+   ```sql
+   -- List all tables in the current database
+   SHOW TABLES;
+
+   -- Search across databases
+   SELECT table_schema, table_name
+   FROM information_schema.tables
+   WHERE table_name LIKE '%users%';
+   ```
+
+2. **Check which database you're connected to:**
+
+   ```sql
+   SELECT DATABASE();
+
+   -- Switch to the correct database
+   USE production;
+   ```
+
+3. **Check case sensitivity:**
+
+   ```sql
+   -- Check the server setting
+   SHOW VARIABLES LIKE 'lower_case_table_names';
+   ```
+
+   | Value | Behavior |
+   |-------|----------|
+   | 0 | Case-sensitive (Linux default) |
+   | 1 | Stored lowercase, compared case-insensitively (Windows default) |
+   | 2 | Stored as given, compared case-insensitively (macOS default) |
+
+4. **Run pending migrations:**
+
+   ```bash
+   # Check migration status with your tool
+   flyway info
+   # Or check in Bytebase's change history
+   ```
+
+5. **Check and repair tables after a crash:**
+
+   ```sql
+   -- MySQL 8.0+: check table status
+   CHECK TABLE mydb.users;
+
+   -- For MyISAM tables
+   REPAIR TABLE mydb.users;
+   ```
+
+   ```bash
+   # Check all tables in a database
+   mysqlcheck -u root -p --check mydb
+   ```
+
+6. **Restore from backup if table data is lost:**
+
+   ```bash
+   # Restore a single table from a mysqldump backup
+   mysql -u root -p mydb < backup.sql
+   ```
+
+7. **Verify user privileges:**
+
+   ```sql
+   SHOW GRANTS FOR CURRENT_USER;
+   ```
+
+## Common scenarios
+
+**After server crash or unclean shutdown:** InnoDB tables may show as missing if the redo log recovery didn't complete. Restart MySQL and check the error log (`/var/log/mysql/error.log`) for recovery messages. If the tablespace file (`.ibd`) still exists, InnoDB will usually recover the table on restart.
+
+**During mysqldump or backup:** If a table is dropped by another session while mysqldump is running, the dump will fail with 1146. Use `--single-transaction` for InnoDB tables to get a consistent snapshot.
+
+**In Docker or Kubernetes:** Containers with ephemeral storage lose all data on restart. If you see 1146 after a container restart, the database volume was not persisted. Mount a volume for `/var/lib/mysql`.
+
+<HintBlock type="info">
+
+Bytebase tracks all schema changes with a full [audit trail](https://www.bytebase.com/docs/change-database/change-workflow/), so you can identify when and by whom a table was dropped. For MySQL installation and client setup, see [How to install MySQL client](/reference/mysql/how-to/how-to-install-mysql-client-on-mac-ubuntu-centos-windows/).
+
+</HintBlock>

content/reference/mysql/error/_layout.md

@@ -31,12 +31,18 @@
 
 ## Query Syntax & Logic
 
+### [ERROR 1064 (42000): You have an error in your SQL syntax](/reference/mysql/error/1064-syntax-error)
+
 ### [ERROR 1055 (42000): SELECT list is not in GROUP BY clause and contains nonaggregated column](/reference/mysql/error/1055-select-list-not-in-group-by)
 
 ### [ERROR 1111 (HY000): Invalid use of group function](/reference/mysql/error/1111-invalid-use-of-group-function)
 
 ### [ERROR 1175 (HY000): You are using safe update mode](/reference/mysql/error/1175-using-safe-update-mode)
 
+## Table & Schema
+
+### [ERROR 1146 (42S02): Table doesn't exist](/reference/mysql/error/1146-table-doesnt-exist)
+
 ## Data Integrity
 
 ### [ERROR 1062 (23000): Duplicate entry](/reference/mysql/error/1062-duplicate-entry)

content/reference/postgres/error/42p01-undefined-table-postgres.md

@@ -0,0 +1,93 @@
+---
+title: 'ERROR 42P01: Relation Does Not Exist in Postgres'
+---
+
+## Error Message
+
+```sql
+ERROR: relation "users" does not exist
+SQLSTATE: 42P01
+```
+
+## Description
+
+PostgreSQL raises error 42P01 when a query references a table, view, or other relation that the database cannot find. The full SQLSTATE code is 42P01 (`undefined_table`). This is one of the most common PostgreSQL errors and almost always comes down to one of a few predictable causes.
+
+## Causes
+
+- **Typo in the table name.** `SELCET * FROM uers` fails because the table is actually `users`.
+- **Wrong schema.** The table exists in a non-default schema but the query doesn't qualify it. `SELECT * FROM my_table` won't find `analytics.my_table` unless `analytics` is on the `search_path`.
+- **Case sensitivity.** If the table was created with double quotes (`CREATE TABLE "Orders"`), you must always reference it with the same quotes and casing: `SELECT * FROM "Orders"`. Without quotes, PostgreSQL folds identifiers to lowercase.
+- **Wrong database.** Each PostgreSQL database is isolated. A table in the `dev` database is not visible from a connection to `prod`.
+- **Table not yet created.** Migrations may not have run, or the CREATE TABLE statement failed silently in a script.
+- **Dropped table.** Someone (or a migration rollback) dropped the table.
+- **Missing permissions.** If the user lacks `USAGE` on the schema, PostgreSQL hides the table entirely and reports it as not existing.
+
+## Solutions
+
+1. **Check the table exists and its exact name:**
+
+   ```sql
+   SELECT table_schema, table_name
+   FROM information_schema.tables
+   WHERE table_name ILIKE '%users%';
+   ```
+
+2. **Qualify the schema explicitly:**
+
+   ```sql
+   SELECT * FROM myschema.users;
+   ```
+
+3. **Check and set the search path:**
+
+   ```sql
+   SHOW search_path;
+
+   -- Add the schema to the search path
+   SET search_path TO myschema, public;
+   ```
+
+4. **Handle case-sensitive names:**
+
+   ```sql
+   -- If created with double quotes
+   SELECT * FROM "Orders";
+   ```
+
+5. **Verify you are connected to the correct database:**
+
+   ```sql
+   SELECT current_database();
+   ```
+
+6. **Run pending migrations:**
+
+   If using a migration tool, check that all migrations have been applied. For example:
+
+   ```bash
+   # Check migration status
+   flyway info
+   # Or with Bytebase — check the change history in the project dashboard
+   ```
+
+7. **Grant schema permissions if hidden by access control:**
+
+   ```sql
+   GRANT USAGE ON SCHEMA myschema TO app_user;
+   GRANT SELECT ON ALL TABLES IN SCHEMA myschema TO app_user;
+   ```
+
+## Common scenarios
+
+**In ORMs and application frameworks:** ORMs like Django, SQLAlchemy, or Prisma generate SQL referencing tables by model name. If the migration hasn't run or the model-to-table mapping is wrong, you get 42P01 at runtime. Check `\dt` in psql to confirm the table exists, then compare against your ORM's expected table name.
+
+**In CI/CD pipelines:** A test suite connecting to a freshly created database will hit 42P01 if the schema setup step was skipped or failed. Add a pre-test check that verifies expected tables exist before running queries.
+
+**With [Postgres case sensitivity](/blog/postgres-case-sensitivity/):** A table created as `CREATE TABLE "MyTable"` requires double-quoting everywhere. If you can, avoid double-quoted identifiers entirely and use lowercase names.
+
+<HintBlock type="info">
+
+Bytebase's [SQL Review](https://www.bytebase.com/docs/sql-review/review-rules/) can catch common issues like unqualified table references and missing schema prefixes before they reach production. See also [How to list tables in PostgreSQL](/reference/postgres/how-to/how-to-list-tables-postgres/) for quick ways to verify table existence.
+
+</HintBlock>

content/reference/postgres/error/_layout.md

@@ -23,6 +23,8 @@
 
 ## Schema & Object Management
 
+### [ERROR 42P01: relation does not exist](/reference/postgres/error/42p01-undefined-table-postgres)
+
 ### [ERROR 42P07: relation already exists](/reference/postgres/error/42p07-relation-already-exists-postgres)
 
 ### [ERROR 2B000: cannot drop role because objects depend on it](/reference/postgres/error/2b000-dependent-privilege-descriptors)