Interesting fact: The word "relational" in "Relational Database" does not have anything to do with the relationships between the tables. Relations are the tables themselves. At the time had their raise, data was stored mostly NOT in tables. So if we had to translate the term it would sound something like "Table-based databases" One of the sources: "Relation is essentially a mathematical term for table. The notion of storing data in tables is so commonplace today that it might seem inherently obvious, but there are a number of other ways of organizing databases." - PostgreSQL DB Manual
Ben. Amazing video. I just have a big doubt that maybe you have addressed in other tutorial. I have 3 databases, each of them have a way to relate with the other... For example, in DataBase A (dbA) I have the email of the user and other data, in dbB I have the email of the user and courses the user must do, in db3 I have the user email and the progress of each course the user must do... I want to relate them automatically with the common fields each database share with the others. Is this possible?
Miniextensions is the only one that does this elegantly. I have a way to do this for one additional linked record that is a hack, but works. I will make a video on it. To do so, you need an automation
This is all good, but how do we use the Form to allow entry to linked tables from a single form? What is explained here is manipulating data in the "database". Is there any tutorial related to the Forms?
Great job Ben! An excellent tutorial that we can use to educate new clients on the basics of Airtable.
Thanks David! This was originally part of a course, but I decided it needed to be more accessible. Glad you found it useful
Nice work - AirTable should add "Referential Integrity" options and implement an MS Access Style Queries interface.
Wow, I just stumbled on a goldmine of Airtable info on your channel...
Welcome aboard! Anything you are currently looking for an answer on?
Interesting fact: The word "relational" in "Relational Database" does not have anything to do with the relationships between the tables. Relations are the tables themselves.
At the time had their raise, data was stored mostly NOT in tables. So if we had to translate the term it would sound something like "Table-based databases"
One of the sources: "Relation is essentially a mathematical term for table. The notion of storing data in tables is so commonplace today that it might seem inherently obvious, but there are a number of other ways of organizing databases." - PostgreSQL DB Manual
Very interesting! I did not know this. I like to think of it as the relationships between the tables, but this makes a lot of sense . Very insightful
Ben. Amazing video. I just have a big doubt that maybe you have addressed in other tutorial. I have 3 databases, each of them have a way to relate with the other... For example, in DataBase A (dbA) I have the email of the user and other data, in dbB I have the email of the user and courses the user must do, in db3 I have the user email and the progress of each course the user must do... I want to relate them automatically with the common fields each database share with the others. Is this possible?
This is heavily needed. Thanks Ben!
You are welcome! Glad it helped
how can i use forms to add entries to linked tables from a single form?
Miniextensions is the only one that does this elegantly. I have a way to do this for one additional linked record that is a hack, but works. I will make a video on it. To do so, you need an automation
This is all good, but how do we use the Form to allow entry to linked tables from a single form? What is explained here is manipulating data in the "database". Is there any tutorial related to the Forms?
Forms are just an entry tool. You set up the database the same. You create the form and all the records will be linked.
Correct, and now Airtable has interfaces which are even more powerful than forms. I can make some tutorials on interfaces if needed
Could have been better :)