This library has no fancy logo. It also lacks all cool badges, but what it has is a simple & ready-to-use implementation of mili- and microsecond types for Doctrine ORM/DBAL.
Date and time is hard, databases are hard - a combination of the two is a nightmare. There's a 5+ years old issue describing the problem. To do it properly and across all platforms seems nearly impossible. However, it is possible to do it with a limited scope. This is why this package was created: I personally stepped into that issue many times over the years, and here came the time to stop copying & pasting the same code.
- Install with composer:
composer require owlcorp/doctrine-microseconds-datetime
(it will work across PHP7.0-8+) - Add DBAL types
- If you're using Symfony, edit
config/packages/doctrine.yaml
and add:doctrine: dbal: types: time_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\TimeMicroType time_immutable_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\TimeImmutableMicroType datetime_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\DateTimeMicroType datetime_immutable_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\DateTimeImmutableMicroType datetimetz_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\DateTimeTzMicroType datetimetz_immutable_micro: OwlCorp\DoctrineMicrotime\DBAL\Types\DateTimeTzImmutableMicroType
- If you're not using Symfony check official Doctrine documentation.
-
For ORM, you can use it like so:
<?php declare(strict_types=1); use Doctrine\ORM\Mapping as ORM; #[ORM\Entity] class MicroEntity { #[ORM\Column(type: 'time_micro')] //you can use text names public \DateTime $time; #[ORM\Column(type: TimeImmutableMicroType::NAME)] //or constants public \DateTimeImmutable $timeImmutable; /** * @ORM\Column(type="datetime_micro") Of course, it works with annotations too */ public \DateTime $dateTime; }
See table below. These are combos which I was able to test, and they should cover most of the usecases. If you know about another database engine supporting it and it can be confirmed easily issues are welcome :)
↓ DB ↓ | Type → | time_micro |
datetime_micro |
datetimetz_micro 3 |
---|---|---|---|
PostgreSQL <10 | ✅ | ✅2 | ✅2 |
PostgreSQL 10+ | ✅ | ✅ | ✅ |
MySQL 5.6.4+ | ✅ | ✅ | ❌ |
Oracle-Xe | ✅ | ✅ | ✅ |
Microsoft SQL <2008 | ❌ | ||
Microsoft SQL 2008+ & Azure | ✅ | ✅ | ✅ |
SQLite 31 | ❌ | ||
Other databases | ❔ | ❔ | ❌ |
✅ = full microseconds support (.000000
) | .000
) | ❌ = not supported
Quirks
- SQLite does't support native
TIME
/DATETIME
fields, but internal functions support text-based representation with milisecond precision. - Older PgSQL in certain edge-cases could loose some precision, you're unlikely to hit the non-Y2K year-2000 bug.
- Bonus: yes, timezone support is broken in most databases. Even where supported you probably shouldn't use it.
Sources