Today was the kick-off of the ZendCon sessions. It started off with a keynote by Harold Goldberg, the CEO of Zend Technologies Inc., and Andi Gutmans who together did a review of PHP's growing role in the enterprise with some case studies.

They also made some announcements:

• Release of Zend Studio 6.1
• Partnership with Adobe
• Release of Zend Core 2.6 for IBM System i
• Dojo integration in Zend Framework
  
  

I'm one of the lucky people at Ibuildings who got to go to ZendCon (2008). I brought my video camera to make some videos of our trip and the conference. The videos of the first 2 days are already online on Youtube, more videos will follow in the next few days. The videos of the first few days cover our trip to Los Angeles where we rented a van to go to San Francisco. You can find the videos here. Make sure you choose the high quality version of the videos, it's a link just below the video.

ATK contains lots of hidden gems. Most of them are hidden because they are undocumented or because they are only documented in the API docs (which nobody seems to read...). In the past few years we've tried to improve the documentation for ATK. We've created a Wiki with lots of how-to's, the "Pizza Guides", a demo application and improved the API documentation. However there are still some features of ATK nobody seems to know about.

In this second iteration of the "ATK's hidden gems" series we will look at a largely unknown feature of ATK's record actions.

ATK contains lots of hidden gems. Most of them are hidden because they are undocumented or because they are only documented in the API docs (which nobody seems to read...). In the past few years we've tried to improve the documentation for ATK. We've created a Wiki with lots of how-to's, the "Pizza Guides", a demo application and improved the API documentation. However there are still some features of ATK nobody seems to know about. In my next few blogs, starting with this one, I will write about some of them.

ATK has built-in test support for a while now. But until now this didn't include support for adding, updating and/or removing test data in such a way that the development/production database isn't littered with test data. You can make use of the mock database class, but then you can't really test if the query you wrote actually works the way it's supposed to work. And you can ofcourse remove the test data in your test by writing the necessary code to do so, but this means a lot of extra work.

As of today there's a third option, you can make use of ATK's built-in test database support.