a new DaDaBIK version is available. Back to work on DaDaBIK after a long parenthesis during which I was mainly doing research and working on my Mentor.FM project.
Version 4.4 beta fixes several bugs (see change log for a complete list).
A new bug related to dates has also been discovered and not yet fixed; not sure if it is correct to call it bug but for sure it can lead to unexpected results, modifying the date values you have in your database. Thanks to Mauri for having reported part of the problem, please look at the known bugs section of the documentation for all the details.
The lack of a locking mechanism has also been highlighted in the documentation, since the current behaviour could lead, in some situations, to unexpected results and data loss.
About the roadmap, the idea is to release a 4.4 final after having found the best possible solution for the dates "bug" and, later, to release a 5.0 alpha which will include a new security model and also provide a locking mechanism.
I am glad to announce that Alessandro Andreoli, an Italian student of the University of Milan, decided to join the DaDaBIK team and to do a very important work on DaDaBIK as part of his master thesis in Computer Science.
Alessandro is working on the new DaDaBIK security model, something I wanted to implement since years but I didn't find the time to.
When his work will be finished, it will be possible to create group of users and to set permissions at a very granual level, for example saying that the group X has read permissions on the table customers while user Y has also write permission on that table, but not on the field customers.phone_number.
It is a very important shift toward the adoption of DaDaBIK in an enterprise environment.
A big "thank you!" to Alessandro from all the DaDaBIK community.
Another big news is that I'm writing from the United States, where I'm going to live for some months as a visiting scholar at UC Berkeley.
I Hope to give you some news about the next release of DaDaBIK soon!
the locking mechanism is the feature chosen among all the ones proposed by users in the Like, disLike and Propose Wiki.
I want to discuss the implementation details with the users so please leave your comments in the Wiki! Registration is not mandatory to write.
as you probably know, DaDaBIK now supports SQLite. Since February 2 2001, more than 30 SQLite installations have been registered online.
I would like to have feedback (good and bed feedback) from those users, because I'm going to release a new version.
I also remind you that the Like, disLike & Propose Wiki will still be available for one month. Please use it to tell what you like, dislike and propose about DaDaBIK. A feature selected anong the ones proposed will be implemented.
today the DaDaBIK Wiki (http://www.dadabik.org/wiki) opens to anyone who wishes to express his opinion about DaDaBIK.
Like, disLike & Propose is the title of the Wiki and the aim is to allow users to freely and easily tell three things: what they LIKE about DaDaBIK, what they DON'T LIKE and what they PROPOSE for the future releases.
The Wiki is open to anyone, registration is not needed to edit. If you prefer you can register and login, in that case you can also easily sign your edits.
After six weeks since its opening, one of the proposals will be chosen; through the Wiki the DaDaBIK developers together with the users will discuss about high-level aspects of its implementation and finally the developers will implement the proposal as a new DaDaBIK feature.