You are browsing a version that has not yet been released. |
Introduction
What is Doctrine MongoDB ODM?
Doctrine MongoDB ODM (Object Document Mapper) is an object modeling library for PHP applications. It allows developers to map PHP objects to MongoDB documents, enabling an intuitive and structured approach to handling data within a MongoDB database.
Features Overview
- Object Mapping: Map PHP objects to MongoDB documents, with support for embedded and referenced documents. Mapping can be configured using PHP attributes, XML, or PHP code.
- Atomic Updates: Utilizes MongoDB's atomic operators for saving changes to documents, ensuring data integrity and consistency.
- Schema Management: Facilitates schema design and management, ensuring that your MongoDB collections adhere to your data model, their indexes, and validation rules.
- Query Builder: Provides a fluent and flexible query builder that simplifies the creation of simple and complex queries.
- Aggregation Framework: Supports MongoDB's powerful aggregation framework for advanced data processing and analysis.
- Repositories: Offers a repository pattern for encapsulating data access logic and promotes code reusability and separation of concerns.
- Events System: Leverages an events system that allows you to hook into various stages of the document lifecycle for custom behavior.
- GridFS Support: Stores large files and binary data in GridFS buckets.
- Doctrine ORM Integration: Create relations between your Doctrine ORM entities and ODM documents to mix SQL and MongoDB databases.
Example
Here is a quick example of some PHP object documents that demonstrates a few of the features.
1 <?php
use DateTime;
use DateTimeImmutable;
use Doctrine\Common\Collections\ArrayCollection;
use Doctrine\Common\Collections\Collection;
use Doctrine\ODM\MongoDB\Mapping\Annotations as ODM;
#[ODM\MappedSuperclass]
abstract class BaseEmployee
{
#[ODM\Id]
public string $id;
#[ODM\Field(strategy: 'increment')]
public int $changes = 0;
/** @var string[] */
#[ODM\Field]
public array $notes = [];
#[ODM\Field]
public string $name;
#[ODM\Field]
public int $salary;
#[ODM\Field]
public DateTimeImmutable $started;
#[ODM\Field]
public DateTime $left;
#[ODM\EmbedOne(targetDocument: Address::class)]
public Address $address;
}
#[ODM\Document]
class Employee extends BaseEmployee
{
#[ODM\ReferenceOne(targetDocument: Manager::class)]
public ?Manager $manager = null;
}
#[ODM\Document]
class Manager extends BaseEmployee
{
/** @var Collection<Project> */
#[ODM\ReferenceMany(targetDocument: Project::class)]
public Collection $projects;
public function __construct()
{
$this->projects = new ArrayCollection();
}
}
#[ODM\EmbeddedDocument]
class Address
{
public function __construct(
#[ODM\Field]
public string $address,
#[ODM\Field]
public string $city,
#[ODM\Field]
public string $state,
#[ODM\Field]
public string $zipcode,
) {
}
}
#[ODM\Document]
class Project
{
#[ODM\Id]
public string $id;
public function __construct(
#[ODM\Field]
public string $name,
) {
}
}
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
Now those objects can be used just like you weren't using any persistence layer at all and can be persisted transparently by Doctrine:
1 <?php
use Documents\Employee;
use Documents\Address;
use Documents\Project;
use Documents\Manager;
$employee = new Employee();
$employee->name = 'Employee';
$employee->salary = 50000;
$employee->started = new DateTimeImmutable();
$employee->address = new Address(
address: '555 Doctrine Rd.',
city: 'Nashville',
state: 'TN',
zipcode: '37209',
);
$project = new Project('New Project');
$manager = new Manager();
$manager->name = 'Manager';
$manager->salary = 100_000;
$manager->started = new DateTimeImmutable();
$manager->projects->add($project);
/**
* Learn how to setup the DocumentManager in the next chapter.
*
* @var Doctrine\ODM\MongoDB\DocumentManager $dm
*/
$dm->persist($employee);
$dm->persist($project);
$dm->persist($manager);
$dm->flush();
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
The above would insert the following documents into MongoDB collections:
// Project collection
{
_id: ObjectId("6674375a140216f6730b2263"),
name: "New Project"
}
// Manager collection
{
_id: ObjectId("6674375a140216f6730b2264"),
changes: 0,
notes: [],
name: "Manager",
salary: 100000,
started: Date("2024-06-19T14:30:52.557Z"),
projects: [
{
$ref: "Project",
$id: ObjectId("..2")
}
]
}
// Employee collection
{
_id: ObjectId("6674375a140216f6730b2262"),
changes: 0,
notes: [],
name: "Employee",
salary: 50000,
started: Date("2024-06-19T14:30:52.557Z"),
address: {
address: "555 Doctrine Rd.",
city: "Nashville",
state: "TN",
zipcode: "37209"
}
}
If we update a property and call ->flush()
again we'll get an
efficient update query using the atomic operators:
The above code would produce an update to Manager's collection that looks something like this:
{
$inc: { changes: 1 },
$set: {
notes: [
"Gave user 100k a year raise"
],
salary: 200000
},
}
{
$push: {
projects: {
$each: [
{
$ref: "Project",
$id: ObjectId("6674375a140216f6730b2265")
}
]
}
},
}
This is a simple example, but it demonstrates well that you can transparently persist PHP objects while still utilizing the atomic operators for updating documents! Continue reading to learn how to get the Doctrine MongoDB Object Document Mapper setup and running!
Setup
A prerequisite of using the Doctrine MongoDB ODM library is to have the MongoDB PHP extension installed and enabled. See the official PHP manual for download and installation instructions.
Before we can begin, we'll need to install the Doctrine MongoDB ODM library and its dependencies. The easiest way to do this is with Composer:
$ composer require "doctrine/mongodb-odm"
Once ODM and its dependencies have been downloaded, we can begin by creating a
bootstrap.php
file in our project's root directory, where Composer's
vendor/
directory also resides. Let's start by importing some of the classes
we'll use:
The first bit of code will be to import Composer's autoloader, so these classes can actually be loaded:
Note that instead of simply requiring the file, we assign its return value to
the $loader
variable. Assuming document classes will be stored in the
Documents/
directory (with a namespace to match), we can register them with
the autoloader like so:
Ultimately, our application will utilize ODM through its DocumentManager
class. Before we can instantiate a DocumentManager
, we need to construct the
Configuration
object required by its factory method:
Next, we'll specify some essential configuration options. The following assumes
that we will store generated proxy and hydrator classes in the Proxies/
and
Hydrators/
directories, respectively. Additionally, we'll define a default
database name to use for document classes that do not specify a database in
their mapping.
1 <?php
// ...
$config->setProxyDir(__DIR__ . '/Proxies');
$config->setProxyNamespace('Proxies');
$config->setHydratorDir(__DIR__ . '/Hydrators');
$config->setHydratorNamespace('Hydrators');
$config->setDefaultDB('doctrine_odm');
spl_autoload_register($config->getProxyManagerConfiguration()->getProxyAutoloader());
2
3
4
5
6
7
8
9
10
11
The last call to |
The easiest way to define mappings for our document classes is with attributes. We'll need to specify an attribute driver in our configuration (with one or more paths) and register the attributes for the driver:
At this point, we have everything necessary to construct a DocumentManager
:
The final bootstrap.php
file should look like this:
1 <?php
use Doctrine\ODM\MongoDB\Configuration;
use Doctrine\ODM\MongoDB\DocumentManager;
use Doctrine\ODM\MongoDB\Mapping\Driver\AttributeDriver;
if ( ! file_exists($file = __DIR__.'/vendor/autoload.php')) {
throw new RuntimeException('Install dependencies to run this script.');
}
require_once $file;
$config = new Configuration();
$config->setProxyDir(__DIR__ . '/Proxies');
$config->setProxyNamespace('Proxies');
$config->setHydratorDir(__DIR__ . '/Hydrators');
$config->setHydratorNamespace('Hydrators');
$config->setDefaultDB('doctrine_odm');
$config->setMetadataDriverImpl(AttributeDriver::create(__DIR__ . '/Documents'));
$dm = DocumentManager::create(null, $config);
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
That is it! Your DocumentManager
instance is ready to be used!
Providing a custom client
Passing null
to the factory method as first argument tells the document
manager to create a new MongoDB client instance with the appropriate typemap.
If you want to pass custom options (e.g. SSL options, authentication options) to
the client, you'll have to create it yourself manually:
1 <?php
use Doctrine\ODM\MongoDB\Configuration;
use Doctrine\ODM\MongoDB\DocumentManager;
use MongoDB\Client;
$client = new Client('mongodb://127.0.0.1', [], ['typeMap' => DocumentManager::CLIENT_TYPEMAP]);
$config = new Configuration();
// ...
$dm = DocumentManager::create($client, $config);
2
3
4
5
6
7
8
9
10
11
12
Please note the typeMap
option. This is necessary so ODM can appropriately
handle the results. If you need the client elsewhere with a different typeMap,
please create separate clients for your application and ODM.