Vladev beat me too it, but here's some further reading in case you want to be able tell your design patterns apart:
P of EAA: Table Data Gateway
P of EAA: Row Data Gateway
P of EAA: Active Record
Object-relational mapping - Wikipedia, the free encyclopedia
There has been some talk about adding an active record implementaiton in the framework, but I don't see how the lack of active record should keep anyone from not building a robust application with ZF.
And for all the praise rails has recieved lately, many of its design pattern implementations are not ideal, or even an example of best practice. Its a great framework, don't get me wrong, but Zend is not going to be swayed by what the cool kids are doing. The vision they have for ZF - and the approach they are taking with coding to that vision - is quite deliberate. This means that once ZF finally matures, it will be one hell of a force to be reckoned with - in my opinion.
If you want a rails like experience, try CakePHP (which I also like).