Support a database table

https://help.lucid.co/hc/en-us/articles/32108180675220-Assign-Lucid-fields-to-your-data
Looks like something similar is already introduced. “Lucid fields”.
Looks like you need an Enterprise account for that as well.
I am referring to making a possible database table feature available to the general public in Lucidspark so it excites general users and entice users from Notion or Craft or xTiles to come over and try it out. There should be no “wall” between the feature and users. 
Also a possible database table feature should be baked into Lucidspark just like the dynamic table or regular table and shouldn’t require integration. 
Integration can still be possible as an add-on but not as a requirement anymore to start. This “wall” should be removed as well. 

Hello.
What if Lucidspark stepped into the database arena with apps like Notion and Coda already existing there? What if the dynamic table feature was retconned to become a database feature so we can use a database on a true infinite canvas in comparison to an infinitely long page? 
What if the table part of the dynamic table became a table view instead? What if the monthly calendar template was added as a view? What if the timeline feature was added as another view? The dynamic grid part of the dynamic table could be reintroduced as a kanban view with columns and swimlanes.

Lucidspark already has what I am looking for(first image)…but could this table be repurposed and rereleased as a dedicated featured for a Lucidspark board? Miro already has a similar feature available for their boards(second image). I took the table and added it to a Lucidspark board (third image) so you have a general idea of what I am referring to.
Regular tables? ✅ Dynamic tables? ✅ Database tables? 🥳

What if the card details for a Lucid card had the same property types as the table so we can drag and drop them onto the table?

Hi ​@patrickpereira1988, thanks so much for your additional comments and ideas added to this thread! Our product team is regularly reviewing feedback within this space as they research product enhancements and new features 

Lucidspark is partially there.
We can move Lucid cards from the Dynamic Table to the Timeline feature and it will adapt its shape. The same goes the other way around. Also if you create a frame or container with the assisted layout feature turned on the Lucid card will also adapt its shape when you move it to and from the Dynamic Table and Timeline feature. 
So that’s three views on a Lucidspark board that a Lucid card can move seamlessly and dynamically to and from- a gallery view, timeline view and a Kanban board view. 
So why not push it even further? Introduce a dynamic monthly calendar view that the Lucid card can work with as well plus a different table view where we can see each property and field for each card laid out instead of one for the column and row header on the Dynamic Table feature. 
Databases are typically found on a document or page that is infinitely linear plus you have to switch tabs or pages to move to another view. 
With Lucidspark there is an opportunity to eliminate context switching, provide an overview with all of them laid together as if they were on a tabletop and provide users with the ability to move Lucid cards seamlessly from one view to another like magic.