Mail Archives: djgpp/2004/08/08/10:03:10
>
> From: boohiss <boohiss AT cubesource DOT net>
> Date: 2004/08/07 ù PM 11:10:38 GMT+03:00
> To: djgpp AT delorie DOT com
> Subject: Re: database library?
>
> On Sat, 07 Aug 2004 19:32:03 GMT, Brian Inglis
> <Brian DOT Inglis AT SystematicSw DOT Invalid> wrote:
>
> > ISTR seeing a version of Btrieve released recently somewhere -- here,
> > Linux, GNU?
>
> Thank you for responding, Brian.
>
> I did some poking around on the web, and Btrieve seems to be right up my
> alley,
> except that I could only find the library pre-compiled for Borland C++ and
> no source
> code to try to compile it with DJGPP. I will continue to look, of course.
>
hi boohiss,
as i am to be blamed for both the port of sqlite and of btrv to djgpp, i thank you to have considered using my work.
as a general rule of thumb, the btrieve api may allow you access to very atomic functionality against the btrieve server, and more sophisiticated operations will require hard work on your side.
here you have direct binary data io with the record manager. there should be a gain in performance, but take into account that btrv port to djgpp is working much harder (and therefore slower) than it's real mode counterparts.
don't forget btrieve itself is commercial software sold by pervasive.
on the other hand, the sqlite api is much simpler, and with the same effort on your side, you can perform complex data manipulation and querying.
performing an sql query prorovides a printf like interface, and the result may be collected in an array of char *'s.
although parsing values from strings is more time consuming than reading into binary form, the number of records to sequentially scan can be highly reduced using sql.
just to take into consideration the prospective growth of your software project, i believe you will surely exploit sqlite better than btrieve, for most normal usage.
thanks again,
alex
- Raw text -