unable to create new mysql table via db_models.py

[guiweit]

pls kindly advise why cannot to add new table from db_models.py as below

class UserTenantKB(DataBaseModel):
id = CharField(max_length=32, primary_key=True)
tenant_id = CharField(max_length=32, null=False, index=True)
knowledge_id = CharField(max_length=32, null=False, index=True)
status = CharField(max_length=1, null=True, help_text="is it validate(0: wasted, 1: validate)", default="1", index=True)

class Meta:
    db_table = "user_tenant_kb"

[dosubot[bot]]

Hi @guiweit! I'm Dosu and I’m helping the ragflow team.

The most common reasons a new table isn't created from your model in db_models.py are:

• The table creation process in RAGFlow is handled by the init_database_tables function, which scans all subclasses of DataBaseModel and calls create_table(safe=True) for those that don't exist. Your model must be defined and imported before this function runs, or it won't be detected and the table won't be created (source).
• If the database connection isn't properly configured, or if there are leftover files in your MySQL Docker volume, table creation can fail. Some users have fixed this by deleting the MySQL data directory and restarting the service (source, source).
• Migration failures or schema mismatches can also prevent table creation. If you added the model after initial startup, you may need to manually run create_table for your model or ensure migrations are applied (source).

Check your logs for errors during the table creation step, verify your model is present in db_models.py before startup, and confirm your database is healthy and accessible. If you see specific error messages, share them for more targeted help.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[guiweit]

Dear Dosu,

well noted with thanks. shall try based on your kind information.

meanwhile, have one query on the existing function. i tried to rename of the table but seems cannot create as below change on the name of the table such as change from user_tenant to user_tenant_kb

class UserTenantKB(DataBaseModel):
id = CharField(max_length=32, primary_key=True)
user_id = CharField(max_length=32, null=False, index=True)
tenant_id = CharField(max_length=32, null=False, index=True)
role = CharField(max_length=32, null=False, help_text="UserTenantRole", index=True)
invited_by = CharField(max_length=32, null=False, index=True)
status = CharField(max_length=1, null=True, help_text="is it validate(0: wasted, 1: validate)", default="1", index=True)

class Meta:
    db_table = "user_tenant_kb"

[guiweit]

Further to above, still unable to create manually

@DB.connection_context()
@DB.lock("init_database_tables", 60)
def init_database_tables(alter_fields=[]):
if not UserTenantKb.table_exists():
UserTenantKb.create_table(safe=True)

[dosubot[bot]]

When you rename a model's db_table or change its schema, Peewee's create_table(safe=True) will only create the table if it does not already exist—it will not rename or update an existing table. If user_tenant_kb already exists in your database (even with a different schema), create_table will skip creation and log that the table exists. If the schema is outdated, you need to manually migrate (ALTER TABLE) or drop and recreate the table if possible.

Also, make sure your model is imported before init_database_tables runs, or it won't be detected for table creation. Check your logs for any errors during table creation—migration failures or unsynchronized schemas can also block creation, and manual SQL may be required to resolve these issues. For more, see the logic in db_models.py and related issues: source, issue 6334.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[guiweit]

Thank you so much for your kind response. shall confirm and revert.