Database error about tabDoctype doesn't exist

[jankijoshi]

MariaDB [db_name]> SELECT * FROM tabDoctype; ERROR 1146 (42S02): Table db_name.tabDoctype’ doesn’t exist

if I Open mariadb and check for the database and table, it is there

“How do I solve this? The DocTypes I created in my custom app are not appearing in the folder.”

[Vipul_Kumar]

When you are creating new Doctype or any kinds of Customization in existing dictype make sure Developer mode is on .
You can use this command to turn on developer_mode

bench --site site_name set-config -g developer_mode 1

[jankijoshi]

Developer mode is already on

[rahib]

It’s DocType and not Doctype.

[jankijoshi]

Yes, but I am still not able to find the doctype folder in custom application’s folder.

[Vipul_Kumar]

if you can share some screenshots that will be better for us to understand the issue

[jankijoshi]

[Hemil_Sangani]

Make sure that you execute the SQL query in the right path. Go to:

cd <bench_name>
bench mariadb

Then, run the following query to retrieve data from the DocType table:

SELECT * FROM `tabDocType`;

[arun99]

I think MariaDB isn’t recognizing your table, even though it exists. Here’s how you can fix it:

1. Check Case Sensitivity – On Linux, table names are case-sensitive. Run:
   SHOW TABLES;

Ensure you’re using the exact table name.

2. Verify Database Selection – Run:
   SELECT DATABASE();

If needed, switch to the correct one:

USE db_name;

3. Confirm Table Exists – Run:

SHOW TABLES LIKE ‘tabDoctype’;

If it doesn’t appear, check for typos.

4. Check for Corruption – Run:

CHECK TABLE tabDoctype;

If corrupted, try:

REPAIR TABLE tabDoctype;
``` (For MyISAM only)

If the table is InnoDB and corrupted, and a simple repair won’t work. You can use Stellar Repair for MySQL to recover the table and its data.

5. Restart MariaDB – Sometimes, a restart helps:

sudo systemctl restart mariadb

If you’re using Frappe/ERPNext, try:
bench migrate && bench clear-cache