On Mon, 2007-03-19 at 01:46 +0200, Dimitris Servis wrote:
> 2007/3/19, guenther <[EMAIL PROTECTED]>:
> > On Sun, 2007-03-18 at 23:51 +0200, Dimitris Servis wrote:
> > > in my wildest dreams... if you read carefully, *each* file is about
> > > 100-200MB. I now end up wit ha collection of 100-200 of them and need to
> > > bundle in one file....
> >
> > Yes, I did read carefully. 100 (source) files, each 100 MByte, stuffed
> > into a single (target, database) file results into that database file
> > being 100*100 MByte. Considering "possibly 200 or more", this easily
> > could result in a single 64+ GByte file.
> >
> > So, in what way was this meant to be a response regarding my
> > concerns? ;)
> In the sense that the legacy code produces files ~100MB. The collection is
> not legacy, that's what I am trying to setup. Unless I don't understand what
> you mean....
Yes, so you got some legacy app. Which produces new files. And your
approach is to stick all these files into a single file. Fine. Now,
according to what you outlined, the "collection" file is going to be
huge. The question is, if your legacy(?) environment actually can handle
that huge collection file (the SQLite database file).
If you can not handle 40 GByte files, your approach will not work. If
you can not handle files larger than 64 GByte your approach is likely to
hit another wall soon.
Or, to put it in other words: Did you evaluate all existing limitations
other than "keep the legacy app"? Did you ever do a dry-run, before
starting to code the real project?
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
