4.0.0 includes fixes for table, index and record locking, MDX index file support and builds with CMAKE. Various misc bug fixes.
Version 3.1.1 tarball was uploaded.
This release fixes some known bugs, provides 64 bit file support and is a general clean up of code. The current CVS tree on sourceforge is not current. This tarball file has the current code.
Also note that multi user file and record locking is not working correctly in this version.
Gary
I'm currently working on version 3.0
If you need the latest version - you can send me an email and I can send you a copy. There are many updates coming in the next release. Index bug fixes, table and index locking updates, memory leaks cleaned up etc.
Gary - gkunkel@zhsac.com
Xbase 2.1.0 released. The library was updated to support newer versions of autoconf (2.53) and automake (1.6.3).
No changes to the library code made in this release.
Gary Kunkel (original author of this project) will be working on development release 2.1.x and be providing bug fixes and updates to the code base.
Finally an new release! There is much that should have been done that wasn't, but a new release has been needed for a while...
We have been contacted by a large company who says we can't use "XDB" for our library because they use "XDB" for their stuff. Don't have the time or money to fight them, so the name has been changed back to Xbase.
I have successfully (I think) merged the source code of the xdb 1.2.0 release with the latest CVS source for xBase (1.9.2?). The result is in current CVS. Please test as you can.
I have tagged the 1.2.0 release of xdb as RELEASE_1_2_0, in case you need to work with those sources. I will create a branch for fixes to xdb1.2.0, if necessary, however, please direct new development to the merged source.
XDB Version 1.2.0 has been released. It fixes many problems with the 1.0.0 release.
I think there is a bug with SourceForge relating to module file releases. For instance, there is a current release under "RPM- Binary" but it doesn't show up. Make sure to look
at all module files to be sure.