I like the fact that you'll be maintaining transparency of usage. The advantage that IB brings is a quality open source db that is available on a large variety of platforms. Example: at work I am constrained to use Win95, at home on my development machine I will use Linux. IB is there on both. IB is also distributable with the same freedom as Zope. Neither Oracle nor MySQL are. It would be nice if one of the options was as available and as free(dom) as Zope. I know there are advocates of both of the other db's and that like MS one could probably say 'no ones been fired for buying/recommending Oracle'. Jimmie Houchin At 9:22 PM -0400 5/3/00, Chris McDonough wrote:
Will this be db agnostic or be fairly hardcoded?
Work seems to be initially towards Oracle and MySQL, but the intention is to abstract commonalities into a base class that would make it fairly easy to use any SQL database.
There are people on the IB lists which are Zope aware and would like to see IB be a first class citizen in the Zope community. I am not an expert on IB, but from what I've seen it could possibly support objects well. It has an understanding of the OO world.
Interbase is also an option... I'd love to use it.. it may be part of development.
It would be nice if this could be done where it could scale from the 'whats sql' user to the power sql user. Giving both the ability to use it at their level. What I mean here is that it is transparent as possible while providing as much expressiveness as possible.
It will be indistinguishable from a FileStorage as far as the user is concerned. It won't allow you to make use of zope object instance data outside Zope, however, as it will still store objects in pickled format.