A small database like SQLite might be useful if you need to be able to store the information, for retrieval at a later date. If the data is fairly static, it might not be worth going to the trouble of plugging in a fully-fledged database. (ie. you could stick it in a text file, and load it)
If the data changes over time, or perhaps you want to add to the data as time progresses, a database can be useful. (insofar as that is what it is designed to do).
For small data-sets, a database is overkill.
For large data-sets, it will make your life easier to manage that data.
It would essentially be a list of textual entries. So yes, it wouldn't be too difficult to insert the data into a database.
The database modules simply open a door to easily accessing many different database types through a common interface - rather than having to learn an (often convoluted) API. ;-)
If the data changes over time, or perhaps you want to add to the data as time progresses, a database can be useful. (insofar as that is what it is designed to do).
For small data-sets, a database is overkill.
For large data-sets, it will make your life easier to manage that data.
would it be possible to copy a column at a time of data into a compatible application
It would essentially be a list of textual entries. So yes, it wouldn't be too difficult to insert the data into a database.
The database modules simply open a door to easily accessing many different database types through a common interface - rather than having to learn an (often convoluted) API. ;-)