CODEWITHSUNDEEP
c#database
Bas
Bas

Reputation: 3

C# combined files direct accessable

I am creating a very simple database in C# which I use to store playlists and an overview of all my music. I want to make this C compatible in the future I plan to make this completely text based. The idea is that every text file is a table, and the contents are JSON format where every line of text is a record.

I don't want to have loose files for each database, so I was thinking about something like a zip file. I don't want to extract and compress every time I access a file. Is there someway I can use a stream reader/writer in C# on different files where windows only see one file?

I'm not completely convinced that this is the way to go. So I'm open to suggestions.

Update, Im currently messing around with the "Local database" item in C#. I never payed any atention to it. It could very well be the solution.

Update2, SQLite seems to be very simple. I have some experience with MySQL in the past with some php projects so that will give me a headstart.

Upvotes: 1

Views: 83

Answers (2)

Peter Krassoi
Peter Krassoi

Reputation: 567

Will you ever try to search between your data? Then use a real database manager, in C# the built in local database file is the simpliest choice (if you are familiar with SQL). The zip file is a good choice for data space and compactness (a single file instead of many files) but it is very slow: for each database operation the whole zip file will be reorganized. Even a tar file (without compression) needs a continous reallocation when the content changes, and a zip file needs extra computation and relocation. If you want something what is compressed and still standard, you can use OpenXML (ods or xlsx, does not matter) to store your data but the save operation will be slow and even slower as your database grows.

Upvotes: 0

Gökhan Karabulut
Gökhan Karabulut

Reputation: 51

You want to use a file as a container containing different files? If so, there are a lot ways to accomplish this. These are techniques I used in the past:

  • Zip:

A compressed file, such as Zip is known to behave that way, can be used as a solution for your interest. It is capable to store virtual files. They can vary in size to at least up to 1 Gigabyte (testet, but I currently don't know if there are implementation based size limits).

  • SQLite:

SQLite sounds oldschool, but it stores all database related stuff into one physical file. Creating a database with tables for each virtual file should to the trick. This approach is useful if you know that your virtual files won't use a lot of bytes in size or neither reach any limit of sqlite field datatypes. As your virtual files are going to use textlines, may you can be able to form then into attributes and tuples. This way you can even use SQL specific statements to query and filter your data as you wish to.

There are still more ways to implement that kind of container format by your own, but propably needs to invest more time and work in it than getting effort out of it. Stay tuned for better ideas and may ready to use implementations :-)

Upvotes: 1

Related Questions