I think I used the wrong term earlier. I said database but I suppose really it's an issue of ADT design. Database sounded fitting at the time because the ADT I'm stuck on in the program would be a big container of data. As far as data persistency goes I figured I'd use files stored on the computer hard drive with the program reloading all past records form the files upon booting up.
Are you working in C++? Possibilities are expansive but if its for your own purposes and you dont want to learn mysql you could just go on and store everything in vectors indexed by sequential ids. Write routines to dump them in bulk into a file, and routines to read them all from a file into vectors again. Write your own search query functins that loop through the vectors.
Yeah, c++. Everything you described sounds almost exactly like what I was planning on doing, actually.
With the speed of even a raspberry pi these days efficiency wont be noticeable until you are dealing with many thousands of rows of transactions.
True. I feel like this kind of thinking would lead to sloppy design though. Then again when I'm doing this for a learning exercise the program is gonna be a sloppy work-in-progress anyway.