Sometimes when dealing with compromised records, there are some cases where there is a single category (record attribute) with many more instances than the rest. Take for example, 1 username and 1 password that made possible the leak of 1000 emails, IDs, and account numbers, in this case the username, password, emails, ID and accounts are all compromised records but at the moment of filling the table, this will result in 999 empty cells for username and password categories since integrates expects the same number of records for all the attributes resulting in a messy and unaesthetic table.
My question is, Would be possible to create a second compromised records table to better organize the information according to the number of instances of the information? for example, being able to create one table for username/pass and another with the rest of leaked information.
I’d love to hear your thoughts