Hi there, I have a question for the author of this soft.
The database (catalog) file seems to be very stable and it works excelent.
Did you design it by yourself?
Do you have any tips or any usefull info about that? (I mean to design one)
I'm trying to develop a soft for my work and I really need some suggestions!!
THANKS!!!!
Joshua Kent.
Suggestion
Hi
This is not a real database actually.
It is just a file where I write all the data of the movies.
When opening the file I read the whole file to memory, and when saving I write the memory to disk.
So it is not very efficient.
The main problem is that images are also put in memory when opening the file, so the file size is limited by available memory.
In the next version I will probably put all the movie info in a XML file that I will load, and keep the pictures in a separate file (and read in memory only what has to be displayed, or request)
This is not a real database actually.
It is just a file where I write all the data of the movies.
When opening the file I read the whole file to memory, and when saving I write the memory to disk.
So it is not very efficient.
The main problem is that images are also put in memory when opening the file, so the file size is limited by available memory.
In the next version I will probably put all the movie info in a XML file that I will load, and keep the pictures in a separate file (and read in memory only what has to be displayed, or request)
SQLite
Hi,
Have you thought about using an actual database to store the data?
I am pretty impressed by a little music library software called Musik (http://musik.berlios.de/) that uses SQLite (http://www.sqlite.org/) as the backend and thought that this could also be used in AMC.
Just a suggestion.
Have you thought about using an actual database to store the data?
I am pretty impressed by a little music library software called Musik (http://musik.berlios.de/) that uses SQLite (http://www.sqlite.org/) as the backend and thought that this could also be used in AMC.
Just a suggestion.