Hi Bubble Users,
I’m trying to use Bubble.io to create a ticket-selling app for a train. There are several layers of data objects that need to happen for this and I’ve finally thought of an approach that will be easy. My lowest level of data is a “seat” on a train. Now my first issue presents itself which is assigned seating because each seat is not the “same” and I need to display whether a certain seat has been taken on a given train. I create a series of dropdown inputs arranged in a 5 x 14 grid to represent the train layout. I couldn’t figure out a better way to do this than creating a data object “seat” which will have a unique seat name. I’ll bind this onto my train layout dropdowns and then add individual “seat” data objects as fields in my “platform” which is just a given train. Now the problem as you see probably see is I’m adding 70 “seat” data objects to my “platform” object. I can have up to 3 platforms per hour if the train is busy (210 seats) and up to 9 different trips throughout the day (1890 seats). Last year we sold about 150,000 tickets and we’re anticipating at least the same if not more yearly. Can bubbly.io handle 150,000 new entries in a table per year or is there a better way to structure this seating data so it doesn’t get out of hand?