how do i design a database system for an app?
-
When designing a program and you want it to store its memory content on a hard disk (database) so that one can restore it's memory at a later time, what is the best way to go about this, do i have to design my own storage API's or there is something available? please need some help.:confused:
-
When designing a program and you want it to store its memory content on a hard disk (database) so that one can restore it's memory at a later time, what is the best way to go about this, do i have to design my own storage API's or there is something available? please need some help.:confused:
This question is so basic and so all encompassing it cannot be answered in a forum post. You need to get a very basic book on computer systems and database. If you don't have the conceptual idea of how a database works then you are not going to understand most of the information on the web, it assumes a reasonable level of knowledge. Try browsing SQLServerCentral.com, you may find some early instruction articles there.
Never underestimate the power of human stupidity RAH
-
When designing a program and you want it to store its memory content on a hard disk (database) so that one can restore it's memory at a later time, what is the best way to go about this, do i have to design my own storage API's or there is something available? please need some help.:confused:
Persisting your app's state (like Window state, position, etc.) and persisting the data your app is working with (business data like Customer Info, Orders, etc.) are two different things. For persisting app state, you can use XML, plain text files, etc. For persisting business data, you can use a database. If the size of the data you're talking about is very small, you can use XML for that too.
-
When designing a program and you want it to store its memory content on a hard disk (database) so that one can restore it's memory at a later time, what is the best way to go about this, do i have to design my own storage API's or there is something available? please need some help.:confused:
BupeChombaDerrick wrote:
store its memory content on a hard disk
I recommend writing it to a binary file.
-
Persisting your app's state (like Window state, position, etc.) and persisting the data your app is working with (business data like Customer Info, Orders, etc.) are two different things. For persisting app state, you can use XML, plain text files, etc. For persisting business data, you can use a database. If the size of the data you're talking about is very small, you can use XML for that too.
Shameel wrote:
If the size of the data you're talking about is very small, you can use XML for that too.
Hey i thought XML was a standard, OpenCV 2.2 uses mostly XML files for storage, so i was actually considering XML, I want to know why i should not use XML for all storage purposes?XML is cool & easy to work with:cool: I actually want to increase the database size of an image indexing software that indexes images based on content for a Content-based Image Retrieval System i have developed so that a huge image database can be indexed, i have been using OpenCV 2.2 storage system for now, I don't know if you have used OpenCV 2.2 storage system, if you have,is it wise to keep using OpenCV 2.2 storage system even for a large data set? :)
-
Shameel wrote:
If the size of the data you're talking about is very small, you can use XML for that too.
Hey i thought XML was a standard, OpenCV 2.2 uses mostly XML files for storage, so i was actually considering XML, I want to know why i should not use XML for all storage purposes?XML is cool & easy to work with:cool: I actually want to increase the database size of an image indexing software that indexes images based on content for a Content-based Image Retrieval System i have developed so that a huge image database can be indexed, i have been using OpenCV 2.2 storage system for now, I don't know if you have used OpenCV 2.2 storage system, if you have,is it wise to keep using OpenCV 2.2 storage system even for a large data set? :)
Yes, XML is a standard and can be helpful for storing relatively small data without the overhead of using a database. But if the size of the data is very huge, performance will suffer. A properly designed RDBMS database will be really fast even if the data is very huge.
-
Yes, XML is a standard and can be helpful for storing relatively small data without the overhead of using a database. But if the size of the data is very huge, performance will suffer. A properly designed RDBMS database will be really fast even if the data is very huge.
Thanks for the answers,i really appreciate that. :)
-
Thanks for the answers,i really appreciate that. :)
As a caveat on Shameels comment, if you have a small number of records and each record is large (image file) then xml may be valid. You imply you have a huge image set to manage. You really should look into strategies of image storage there are quite a number of options.
Never underestimate the power of human stupidity RAH