I'm currently pretty happy with Supabase where my DB is hosted, as I'm the only person who needs to access it. I'll let you know if/when I need to expand!
FWIW, virtual columns and tables are pretty easy in Django. AJAX-ify the forms seems to be possible but the packages tend to be pretty out of date.
Obviously you product has value for non Django teams, but tbh it's not clear to me this project is a win over django-admin for me (someone who reaches for that as my first tool to solve this problem). And some of the rough edges are not that big of an issue for me personally, not enough to add unknown risks w/ a new technology.
It does look great, however - hopefully this feedback is useful because I definitely don't mean to crap on your service.
Comments
I'm currently pretty happy with Supabase where my DB is hosted, as I'm the only person who needs to access it. I'll let you know if/when I need to expand!
FWIW, virtual columns and tables are pretty easy in Django. AJAX-ify the forms seems to be possible but the packages tend to be pretty out of date.
Obviously you product has value for non Django teams, but tbh it's not clear to me this project is a win over django-admin for me (someone who reaches for that as my first tool to solve this problem). And some of the rough edges are not that big of an issue for me personally, not enough to add unknown risks w/ a new technology.
It does look great, however - hopefully this feedback is useful because I definitely don't mean to crap on your service.
Not at all :)
Do you have a link or instructions on how to create virtual columns in Django Admin?
I'd just use a calculated virtual column that you calculate at the queryset retrieval time. (Note I am not an Django expert, more of a hack).
https://www.appsloveworld.com/django/100/228/add-calculated-...
Ah, this is an overloading of terms. Plato virtual columns are not computed columns. They're new storage.