Edit: I think i used the wrong word here. By "sequential" i don't mean that everything aid 1 enters has to be in the order of the time at which they enter it.
What i mean is that they should be clubbed together in the table that's it.
Suppose there are tables A and B.
A is linked to table B that stores data which may be repeated for a user. Each user may have 0 or 1 or 2... or n(limit) number of data is table B.
But the data is not entered sequentially because it totally depends on if/when the user chooses to enter it, how many data they enter.
So if user with aid 1 enters "lol" today, and then user with aid 2 enters ":)" tomorrow,and then 1 enters xd day after tomorrow then the data will be stored in the same manner i.e.
| bid | data3 |
|:-----------|------------:|
| 1 | lol |
| 2 | :) |
| 1 | xd |
Is there a better way to do this? Maybe the way i am storing data is wrong.
Or maybe the table can to optimized in some way like making the rows with same id to be sequential i.e. one after the other such that there is no row with a different id between 2 rows with the same id.
timestamp default current_timestamp
seems to be enough) into table B structure. – Akina Aug 6 '18 at 13:11