BTree Library and Faircom's CTree.

[Tony Olekshy]

This is crossposted to the newsgroups in which a number of questions have
been posted regarding BTree/ISAM packages and the CTree product from Faircom.
Please followup to comp.databases.

I have been using CTree from Faircom for over 3 years, and am quite happy
with the product.  RTree is ok, and I don't use DTree (I wrote my own over
the last three years, which is, of course, tailored to our exact needs).

CTree manages your open file pool, so there is no limit to the number of
relations you can have open at once.  You also have full control over other
limits, such as max key len, 'cause you have the source code.  In server mode,
CTree has only one process accessing the disk files, so read/update locking
works properly even if your OS doesn't know how to do it.

There are no relicensing fees, which is why we didn't use INGRES.  There are
some SQL front ends being developed (such as CQL from Machine Independent
Software Corporation), but as far as I'm concerned SQL is useless without
INGRES-style query optimization, and we already decided we couldn't afford the
INGRES relicensing fees in our vertical market.

We have ported CTree and our source code to DOS, UNIX, XENIX, and VMS.
I have found Faircom's support to be quite good, when I have found tough
questions Fairman himself took the time to help me solve the problem.

I have no affiliation with Faircom other than as a satisfied customer.
I do however run the CTree mailing list...

    Send mail for the next digest to ctree at oha.UUCP or ...!alberta!oha!ctree.
    Send administration mail to ctree-request at oha.UUCP or ...!ctree-request.
    If nothing else works, try Tony Olekshy at ...!tony or +1 403 425 9657.
    Opinions expressed in the ctree mailing list are those of the authors of
    each piece of mail.  This mailing list is not associated with FairCom.

Yours, etc., Tony Olekshy (...!alberta!oha!tony or tony at oha.UUCP).