Just to confirm, if i change the type to DATETIME vs DATETIMETZ then i dont
get this additional query. But it's confusing to me as to why it happens.
is this a bug or expected behaviour?
On Thursday, May 4, 2017 at 12:33:40 PM UTC+1, Andrew Davey wrote:
>
> I've noticed this for a while now and i'm unsure what the issue is and
> what it's happening.
>
> if i were to have no changes in my entity but run doctrine:schema:update
> --force i would always have 1 query executed. I'm now using diff with
> migrations to keep on top of my DB changes vs. using schema:update and it's
> always adding the following SQL update:
>
> $this->addSql('ALTER TABLE table_name CHANGE deactivatedDate deactivatedDate
> DATETIME DEFAULT NULL');
>
>
> the entity property definition is:
>
> /**
> * @var \DateTime
> *
> * @ORM\Column(name="deactivatedDate", type="datetimetz", nullable=true)
> */
> private $deactivatedDate;
>
>
> Now i'm looking at this properly Is it the datetimetz thing? But if so why
> is this happening?
>
--
You received this message because you are subscribed to the Google Groups
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.
