Types of Data Persistence

[jdipierro]

Hey all,

I'm working on a program that I need data persistence with, and I was wondering what options I had?

I know that I can read/write text files but I don't feel that's the best method for the program I'm trying to create (something to help me keep track of credit card spending)

The only other method that I know for persistence is to use a database, but I was wondering one thing:

If I were to send the program to someone else to use, would they have to install a database program on their computer? If so is there any alternative to a database for storing information?

I don't quite understand how programs store data if it's not written in a plain text file, and not stored in a database.

[travishein]

A lot more recent open office kinds of documents use a complicated XML type of file structure.

[Eranga]

If I were to send the program to someone else to use, would they have to install a database program on their computer? If so is there any alternative to a database for storing information?

It depends on the way you want to design your application.

One possible way is, if you don't like to keep a database on clients' PC, keep a central database in a server and communicate with it. But the problem is that all of your clients need to be connect to the internet. Best way to communicate is though web services, using XML streams.

[Tolls]

I wouldn't recomend a central store, even if you aren't suppliyng this to clients and are only doing this for friends/colleagues. This is simply because financial data might be considered "sensitive".

Keep it locally, which you've already thought comes down to a database or some form of text file (either plain, xml, whatever). The decision on what to do there is then a case of what it is this thing is intended to do...and what your knowledge areas cover...and if you are using this as a learning exercise.

Me? I'd use a database, but then I know what I'm doing in that field, and I could probably code it faster than xml, which would be my second choice (albeit a bit distant).

[Eranga]

I agreed that use of a central store is not a good idea, specially when you want to log transaction details. Have to use replicas within a distributed store. But maintaining that is not an easy task at all.

[Eranga]

Me? I'd use a database, but then I know what I'm doing in that field, and I could probably code it faster than xml, which would be my second choice (albeit a bit distant).

In most of the case I use XML to store data, and to transfer as well. Main advantage I've seen is that system independent and vendor independent standard.