From a5cfd2321f06435a86177663ea5fdc7b855b2c3d Mon Sep 17 00:00:00 2001 From: Benjamin Eberlei Date: Sun, 5 Jun 2011 17:21:11 +0200 Subject: [PATCH] Document Mssql Datetim2 behavior --- en/reference/limitations-and-known-issues.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/en/reference/limitations-and-known-issues.rst b/en/reference/limitations-and-known-issues.rst index 3a042cfa9..64134251c 100644 --- a/en/reference/limitations-and-known-issues.rst +++ b/en/reference/limitations-and-known-issues.rst @@ -316,3 +316,8 @@ support all CRUD operations on views that semantically map to certain tables. You can create views for all your problematic tables and column names to avoid the legacy quoting nightmare. +Microsoft SQL Server and Doctrine "datetime" +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Doctrine assumes that you use DateTime2 data-types. If your legacy database contains DateTime +datatypes then you have to add your own data-type (see Basic Mapping for an example). \ No newline at end of file