- What data is stored in what tables?
- What type and size of data is valid for a given field?
- How are the various tables connected to each other?
Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide.
We made a few major changes to the v1.7 search interface for a big improvement in performance. The first change was to ot use a wildcard for the prefix. Thus when a user searches on NAME, we only search for 'NAME%', in older version we would search for '%NAME%'. This allows mysql to use the index on sort_name and is significantly faster than a full table scan. The second change involved not searching the 'email' table when doing a search on 'name'. This allows us to avoid two very expensive 'LEFT JOIN' sql statement and speeds up search significantly.
You can get around the...Read more
USPIRG has decided to work on CiviCRM as the Code for Change project this summer!. Should be a great value add to the CiviCRM community. Thanx to Wes Morgan and USPIRG for choosing CiviCRM. From their website:
Code for Change is an exciting new program which brings together computer science students and recent graduates in the summer to lead an open source software development project. The projects will vary from year to year, but they'll tend to focus on furthering the online organizing work of U.S. PIRG and, being open source, lots of other organizations as well.... Read more
Other release highlights include:
The nice thing about developing software is that the work is never done. There are so many cool things that we can do to make CiviCRM a better application. I've been having some pretty good conversations with David Strauss of Four Kitchen Studios on our IRC channel (#civicrm at irc.freenode.net). Four Kitchen Studios has been a great resource for CiviCRM and were instrumental in deploying CiviCRM within Wikipedia. In the recent past, David has initiated the de-dupe and contact merge algorithm which we hope to incorporate in CiviCRM v1.8.
CiviCRM v1.7 is proceeding at a good pace. We've closed most of the issues with just a couple that are still open. We've also got a public sandbox that the community can use and test out various features of v1.7. Hopefully this will also allow us to collect a few more bug reports and issues. We definitely would like to see the community step up and play a more crucial role with testing the product before the beta and final release.
If things continue at this pace, I suspect we'll push out a beta candidate mid next week. At that point,...Read more