Hi, let’s say I have a table like “OrderedProduct” with two keys “ProductID” and “CustomerID”, I have already created two relation columns between this table and “Products” and “Customers” ones. Now If in my view I need to show a customer profile image, I have to create another look-up column that refers to the “Image” column from the “Customers” table. Same thing if I need other information from the “Products” or “students” table. This is really time-consuming, is there a way that in the interface, I just select the relationship column and through it, I access all fields of the other table in relation.
Not at the moment, but I believe that this capability is on the roadmap. So, stay tuned…
That would be great; this sort of data-driven app generators are heavily dependent on these relation concept; better facilities provide a better user experience.
Agreed. If you’ve ever worked with relational databases, then this is the behaviour you intuitively expect. ie. Once you’ve established a foreign key relationship between two tables, then you should have direct access to attributes in either table.
Exactly, what make environments like Gilde to be promising is the ability that one can build an app but truly from the database perspective and philosophy. I really have fun with this concept. And Interface builder or the view engine should be smart enough to build relevant possible views based on the given data model. In needs a bit of more intelligence like rule based system or ontological approaches to extract meta data about the database by looking to tables, and columns names. Then make smart guesses based on that. For instance when there is a “start date” and “end date” column or any other semantically similar terms, then the view engine should bring up a nice date range picker rather that we use tables and add extra columns to manage it. Btw this is the trend, I can see in couple of years many improvements will be around. And hopefully NoSQL models also come to the game, plus the ability to export the whole project into a well structured code base.
Glide already does this to some extent. For example, when you first point Glide at a spreadsheet (or create a new Glide tab), it will make some educated guesses at the data types and add appropriate components to the layout.
U right I noticed that, its really interesting to see, database again governing the entire article of an application! Its not anymore app agnostic anyway looking forward for more features and improvements in this field.