Right now if you add fields, you'll automatically get that new column of data added. We haven't added a way to delete fields yet, so if you remove fields, you'll still see the old data in there.
It basically allows you to do what you are doing without having to manage tables by adding and removing columns.
The idea is simple, preemptively create a table with a certain distribution of column types and then allow the developer to define models in their app and map properties of their model to available columns.
It is a pretty robust idea and works well, we use it in our product.
I'll be doing a thorough write up on it sometime in the near future.
Comments
It automatically creates the schema based on the form data :)
cool, what happens if I change the form?
Right now if you add fields, you'll automatically get that new column of data added. We haven't added a way to delete fields yet, so if you remove fields, you'll still see the old data in there.
You might be interested in our "Preemptive Schema Data Modeling" technology (http://crudzilla.com/doc/eu-doc/#data-modeling )
It basically allows you to do what you are doing without having to manage tables by adding and removing columns.
The idea is simple, preemptively create a table with a certain distribution of column types and then allow the developer to define models in their app and map properties of their model to available columns.
It is a pretty robust idea and works well, we use it in our product.
I'll be doing a thorough write up on it sometime in the near future.
Thanks Edmond! We used Firebase's validation rules to create a basic schema but something more robust might be called for in the future.
no problem, feel free to get in touch if you need assistance trying it out.