RE: [Dev-C++] Re: RE: need advice on data storage

[Reid T. <Rei...@at...>]

Big Playah wrote:
> Hi,
>=20
> Reid, what would be the benefit of using an SQL database for
> quite simple data storage? I don't need any features an SQL
> engine could give me, at least not one I know of - related
> data storage, easy searching, good hierarchy. but, I'd add
> quite an overhead, drop in quite some kB of exec data, and
> mix in another language. SQL is no problem for me, I've been
> using SQL DBs succesfully for web pages earlier, and it was
> really fine for storing related data and performing searches
> and sub-selects. this is not the job right now. I'm dumping a
> variable sized memory image and some info about it, that's my
> project file, and I have really just a few variables that
> will be saved as variables - under 20 at first count. user
> works on just 1 project at a time, that's no prob again. I
> don't want to encrypt these save files, but do not want to
> encourage users of hand-editing them. so again, this is not
> an issue. still, I prefer plain one-file saving. one thing,
> I've mentioned I have some selects. namely, I have currently
> 2 of them, each having ~ 6 options, so this does not require
> an SQL engine... so, I'm not wanting to disargue in that SQL
> is good for some jobs, just asking if it would bring me any
> _useful_ benefits which I don't see ?
>=20
> tom

go back to what you originally wrote that you liked/disliked about your
current implementations; throw in this comment "..what do you suggest,
how should I solve this? (I'm quite new to C++ and OOP, previously had
only experience with function programming...) tia, tom.." sqlite was
just a suggestion, it's already implemented, is easy to add as a
component of another application, is fast, saves you from
designing/implementing/debugging a 'from scratch' solution, etc

again, just a suggestion in response to 'what do you suggest, how should
I solve this?'

reid