Hello @an-tao @hwc0919 ,
I am building a low-code platform where administrators can dynamically create database tables, add columns, and establish foreign key relationships (like course_extra.teacher_id → teacher.id) at runtime, without recompiling or restarting the service.
I found that Drogon's ORM requires generating model classes via drogon_ctl, which must be compiled into the binary. This means we cannot dynamically add new tables or relationships in production.
In contrast, frameworks like Spring Boot + JeecgBoot (low-code platform) support dynamic tables by ditching static ORM models and using pure dynamic SQL + Map/JSON structures at runtime.
So my question is:
If I want to build a real low-code platform, should I completely avoid using Drogon's ORM?
And only use native SQL with Result/Json::Value without generated models?
Thank you very much for your clarification.
Hello @an-tao @hwc0919 ,
I am building a low-code platform where administrators can dynamically create database tables, add columns, and establish foreign key relationships (like course_extra.teacher_id → teacher.id) at runtime, without recompiling or restarting the service.
I found that Drogon's ORM requires generating model classes via drogon_ctl, which must be compiled into the binary. This means we cannot dynamically add new tables or relationships in production.
In contrast, frameworks like Spring Boot + JeecgBoot (low-code platform) support dynamic tables by ditching static ORM models and using pure dynamic SQL + Map/JSON structures at runtime.
So my question is:
If I want to build a real low-code platform, should I completely avoid using Drogon's ORM?
And only use native SQL with Result/Json::Value without generated models?
Thank you very much for your clarification.