-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Docs] Update docs regarding "datetimetz" type #6014
Conversation
Shouldn't this target 3.7.x too? |
At first sight, I think no, as it fixes some wrong assumptions. |
78f2f5f
to
27a2d8a
Compare
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
IMO, this is still relevant. |
The base branch was changed.
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
@phansys can you please address the conflict? 🙏 |
I'm currently AFK, but I'll be rebasing today. |
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
* 3.8.x: Connection::setNestTransactionsWithSavepoints() should not break lazy connection (doctrine#6362) [Docs] Update docs regarding "datetimetz" type (doctrine#6014)
Summary
Related to #6006.
BTW, I think we should rename
known-vendor-issues.rst
to something likevendor-specific-caveats.rst
or similar, because many of the behaviors described there are not necessarily issues.ToDo
3.6.x
;