Attention

TYPO3 v8 has reached its end-of-life March 31st, 2020 and is not maintained by the community anymore. Looking for a stable version? Use the version switch on the top left.

You can order Extended Long Term Support (ELTS) here: TYPO3 ELTS.

Get Blog from the Repository

Lets take a look into the BlogRepository and travel into the inner core of our little action island.

<?php
namespace MyVendor\BlogExample\Domain\Repository;

class BlogRepository extends \TYPO3\CMS\Extbase\Persistence\Repository
{

}

The code is not shortened. The BlogRepository simply does not have any own code since all methods which are used very often are already implemented in the parent class \TYPO3\CMS\Extbase\Persistence\Repository. These functions are also available in all child classes. We call the method findAll(), to retrieve all blog objects.

Excursion: The Repository

The way a repository works is much like a library of a university which works in the following way:

You tell an employee of the library to find a book matching certain criteria. After a few minutes till days you get the corresponding book. In this case it doesn't matter to you if the book is right below the counter, in a shelf, in the cellar, or is not even printed yet (except from the time issue - but students have time). It is only important that you get the book at any time. Remarks made with a pencil by you will be added permanently (hopefully without changes) when you return the book.

That is translated to a repository: Via a repository you tell a method to find an object matching certain criteria. After a few milliseconds till seconds you receive the corresponding object. In this case you don't care where the object is stored. Practically it even doesn't matter if the object is stored in the memory, must be fetched from the hard drive, is retrieved via web service from another server, or is instantiated for the first time (except from the speed - but users have time). The only important thing is that the object is instantiated and delivered to you. Object attributes changed by you will be stored when you leave the extension.

Note

Although you don't need to implement your own logic extbase expects an existing class.