Microsoft SQL Server and MSSQL support for microseconds fix #249
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dg
force-pushed
the
master
branch
20 times, most recently
from
29e8b85
to
fe92b3c
Compare
dg
force-pushed
the
master
branch
3 times, most recently
from
cb9fd29
to
4236b80
Compare
dg
pushed a commit
that referenced
this pull request
Jul 21, 2017
|
@hubipe is seems that it fails https://ci.appveyor.com/project/dg/dibi |
|
I have fixed that in commit hubipe@af40450 but don't know, how to refer it to here. |
|
Fixed, thanks |
dg
pushed a commit
that referenced
this pull request
Oct 5, 2017
Pull request #249 forgot about dblib in switch
dg
pushed a commit
that referenced
this pull request
Feb 25, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is fix for pull request #246, which introduced error datatype mismatch error for Microsoft SQL Server.
When I started using microseconds from pull request #246 on production with MSSQL, it started to failing. It was because format for datetime Y-m-d H:i:s.u was assumed by MSSQL to be type DATETIME, which only support 3 decimal numbers for microseconds. Since date in PHP uses for microseconds 6 decimals, MSSQL raised exception datatype mismatch. Therefore when using microseconds for more than 3 decimal numbers, it has to be explicitly casted to type DATETIME2, which supports microseconds for up to 7 decimal positions.