Re:Dynamic Django Models with Model Models
by TylerE on Wednesday August 22, 2018 @01:57PM
(#17820526)
Postgres JSONB columns could give you a lot of that without actually creating seperate tables - for instance indexes over embedded keys.
Re:Dynamic Django Models with Model Models
by ppeetteerr on Wednesday August 22, 2018 @02:56PM
(#17821004)
This. The best of both worlds + you get querying inside of the JSON.
Re:Dynamic Django Models with Model Models
by ubernostrum on Thursday August 23, 2018 @03:30AM
(#17825281)
I once wrote something very similar to this as a literal proof-of-concept hack for a form-oriented problem. It's fun to get it to the point where it works for the simplified test cases such projects always start out with.
But I never used it beyond that proof-of-concept; I still reach for EAV and/or JSON columns when I need to do this sort of thing for production software.
Re:Dynamic Django Models with Model Models
by jackbravo on Wednesday August 22, 2018 @04:17PM
(#17821769)
Something like https://form.io/ ?
I have often wondered about pushing the customizability down a level though, like what the author does here, where each form creates a separate database table. It's too crazy for me, but it's tempting. And I have actually done it before where users' forms automatically generate individual tables in a separate flattened reporting database. It works really well for giving enterprise customers SQL access to an OLAP view of their data, even if I wouldn't use it for my source-of-truth OLTP structure. (Some day I'm going to write a blog post about that.)
Even just for derived reporting tables, you quickly discover all kinds of limits in your database: reserved words, max columns per table, max columns per query, number of foreign keys pointing at a central table, etc. I haven't hit anything fatal though (with Postgres).
Anyway, I'm excited to see that someone actually pulled this off, complete with Django models and migrations, even if it's just for fun.