Hi all! I’m creating an app in which I can login and it runs a series of calculations that generate a new row in a table “Transactions” quite often. The thing is when I have more users using the app, the table will grow a lot (and I’m afraid the performance will decrease). So the table “Transactions” will have a lot of rows corresponding to different users (and mixed).
Is it possible to have a different table for every user (table “Transactions User 1”, table “Transactions User 2”, etc.)? The thing is I’m not sure if it’s possible to create new tables -instead of creating new rows in the same table- dynamically, so one table per new user registered.
As far as I know, you need to create the tables (and their fields) manually, and besides, it would be a nightmare managing a different table for each user. And tables are meant to handle a lot of rows, so you’re okay doing it the conventional way. There may be a case for creating different tables for different types of ‘transactions’, but other than that, I think you want to stick to basics here.
If you end up showing on the front end “Current user’s transactions”, I don’t think that will be a performance issue. Just my 2 cents. Good luck!
As long has you have a list on the User of their Transactions, then Bubble can go directly to the relevant rows. There should not be a performance hit in reading.
Searching through a large table looking for matching users is likely to be slower.
Thanks, guys! The problem is: what if the table updates every 1 minute per user? If I have to access to specific rows in a “for” loop, don’t you think it will be bad for the performance? For example, when I press on a button I created to “delete all transactions”, sometimes it says “App too busy”, like if it was not able to do the calculations correctly… Thanks and looking forward!
