Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?
Self-hosted
What do you need help with?
Hello all,
I would like to learn about databasing and I’d like to start with something very simple as I am a learn-by-doing type.
The plan is to set up a database for pressurised vessels, recording the following:
Vessels: type, serial no, manufacturer, images (up to 3)
Location: building, floor, room number, or if on a roof
I then want to build an application so that people can search or add assets, later I plan to add a login and registration page. It would be good if they could search by any of the recorded data in Vessels or Location.
Ignoring the need to login or register just now, should I split the information (Vessels and Location) into two tables or just put everything in one? I think put the lot into one table.
Thanks,
Nick.
One of the central questions is about the relationship between vessels and locations. Is there always just one vessel at one location? Can a vessel change locations?
If there will be more than one vessel at one location, then you should split it into two tables. If there is only one per location and a vessel doesn’t change location (or you don’t want to track the old location), then you can put them in one table.
However, this question is not related to Baserow technically, but rather to setting up any database.
1 Like
Hello @be_Berlin,
Thank you for your advice here.
The vessels are all fixed, so they will not be moving but may be removed and/or replaced. There will be more than one at each location, but they will never move between them.
Yes, this is a general question regarding structure but one that is important if I am to start off on the right foot, so to speak.
Thank you for your advice and I will get started.
Well, just to update - I have all my data entered with a front end behind a login screen to add more records when needed by others.
Awesome, thank you for getting me started.
1 Like