>>>>> Baruch Burstein writes:
[…]
> My resources are a bunch of sound and image files, level data files,
> script files and other game data stuff. Instead of distributing my
> game with about 20-30 small (some very small) files, I thought I
> would roll all the files into some kind of archive. I started to
> roll my own format, when it occurred to me that sqlite may be well
> suited for this.
The ar(1) archive format [1] may also be considered. In
particular, the Debian project distributes pre-built binaries
for its software in ar archives (known as Debian package files,
or .deb's, there), which consist of a metadata part
(control.tar.gz) and the packaged files themselves
(data.tar.gz.)
However, if the intent is to associate a variety of metadata
with each of the data files, using SQLite seems to me like a
more natural solution.
[1] http://en.wikipedia.org/wiki/Ar_(Unix)
> Which brought me to wonder if storing 5-10 tables with some of them
> having <500 bytes of data may be very inefficient.
Which kind of game data takes so little space, I wonder?
> I don't want to substitute a 20K file for my <10K of files. I know
> this is not a lot, but it still bothers me, like what when I have a
> game with 500M of files? (you never know, it may happen!). No
> searching is needed (except once for the key to load a resource)
--
FSF associate member #7257
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
