From f9715ac24a3cd5392f903f261cdf6dbfd2fc04de Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Gr=C3=A9goire=20Paris?= Date: Tue, 22 Dec 2015 17:44:00 +0100 Subject: [PATCH] Guess missing words --- docs/en/cookbook/working-with-datetime.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/en/cookbook/working-with-datetime.rst b/docs/en/cookbook/working-with-datetime.rst index 3b1e2e59f..660f2bbcf 100644 --- a/docs/en/cookbook/working-with-datetime.rst +++ b/docs/en/cookbook/working-with-datetime.rst @@ -56,7 +56,8 @@ on all this systems. Handling different Timezones with the DateTime Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -If you first come across the requirement to save different you are still optimistic to manage this mess, +If you first come across the requirement to save different timezones you may be still optimistic about how +to manage this mess, however let me crush your expectations fast. There is not a single database out there (supported by Doctrine 2) that supports timezones correctly. Correctly here means that you can cover all the use-cases that can come up with timezones. If you don't believe me you should read up on `Storing DateTime