Jun-20-2019, 06:48 AM
Hi,
generally speaking, you can store anything into any data base. Just sometimes it's difficult to make data structures fit, thus some data bases don't make too much sense for certain structures.
The decision should also be based on which values you want to be able to query in the end.
In case you want to use a RDBMS, I would suggest two tables: one for the MainID and one for the address, whereas the tables may have a one-to-many relation.
Plan B would be to transfer the data set to JSON - which is easy - and store in a data base which accepts JSON. Like MongoDB or PostgreSQL.
Regards, noisefloor
generally speaking, you can store anything into any data base. Just sometimes it's difficult to make data structures fit, thus some data bases don't make too much sense for certain structures.
The decision should also be based on which values you want to be able to query in the end.
In case you want to use a RDBMS, I would suggest two tables: one for the MainID and one for the address, whereas the tables may have a one-to-many relation.
Plan B would be to transfer the data set to JSON - which is easy - and store in a data base which accepts JSON. Like MongoDB or PostgreSQL.
Regards, noisefloor