SOTD: Prefered Storage
-
Survey of the Day What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Programmer: A biological machine designed to convert caffeine into code.
Developer: A person who develops working systems by writing and using software. [^]if it's less than 100 items, i assume the user can just re-enter the data each time the app's run. keyboards are getting easier to use every year. a modern keyboard makes data entry almost pleasant!
image processing toolkits | batch image processing | blogging
-
Flat binary files. Preferably in opposite endianness. This data must also be compressed using a shockingly poor proprietary compression method.
HalfWayMan wrote:
This data must also be compressed using a shockingly poor proprietary compression method.
maybe Base64-encoding? it features an impressive 3:4 compression ratio.
image processing toolkits | batch image processing | blogging
-
I think XML files will be good.
------------------------------
"The Soapbox has been so ..."<Response> <Name>Chris Losinger</Name> <Msgtext> I 4<super>th</super> it! </Msgtext> </Response>
image processing toolkits | batch image processing | blogging
-
Survey of the Day What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Programmer: A biological machine designed to convert caffeine into code.
Developer: A person who develops working systems by writing and using software. [^]jason_lakewhitney wrote:
for an application where the data to be stored is minimun?
random access in real-time? or load and forget? or load and in-memory retrieve? random access to disk in real-time you want an indexed database, either a light SQL, or a self-built (many libraries out there for b-tree, m-tree, etc indexing). You want to choose something for rapid reading, including binary files if the data is indexed sequentially and doesn't need to be resorted. (though the latter is frowned upon -- go for the light SQL) load and forget or in-memory retrieve after load works great for XML. the right tool for the right job. :)
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Survey of the Day What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Programmer: A biological machine designed to convert caffeine into code.
Developer: A person who develops working systems by writing and using software. [^]If it's only a few hundred KB, max, i'll go with XML. XML's fairly easy, saves me writing a complicated parser, and allows a fair bit of structure to be represented. Also, it's easy to use XSLT to generate reports, or use a text editor to view or tweak...
---- Scripts i’ve known... CPhog 1.8.2 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.2 - printer-friendly forums Expand all 1.0 - Expand all messages In-place Delete 1.0 - AJAX-style post delete Syntax 0.1 - Syntax highlighting for code blocks in the forums
-
<Response> <Name>Chris Losinger</Name> <Msgtext> I 4<super>th</super> it! </Msgtext> </Response>
image processing toolkits | batch image processing | blogging
-
Survey of the Day What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Programmer: A biological machine designed to convert caffeine into code.
Developer: A person who develops working systems by writing and using software. [^]Index cards. Small, compact, easily indexed and searched and not susceptible to the occassional EMP.
Happiness is knowing that somewhere out there, there is a bullet with your name on it.
-
Survey of the Day What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Programmer: A biological machine designed to convert caffeine into code.
Developer: A person who develops working systems by writing and using software. [^] -
jason_lakewhitney wrote:
What type of storage do you prefer to use for an application where the data to be stored is minimun? i.e.: records < 100
Just display the data on the screen and give the user 5 seconds to take a photo of it.
-
Flat binary files. Preferably in opposite endianness. This data must also be compressed using a shockingly poor proprietary compression method.
-
Without reading the other responses and since you said "records" adn "data" I'm assuming you don't mean an ini file type data. I'd store it as xml, there really isn't any other choice worth doing is there?
Yeah, XML. And VS 2005 projects have a "Settings" page which may be of use.