Fix #12814 : Allow length parameter to be specified for DATETIME and TIME #12815

merged 2 commits into from Dec 20, 2016


None yet

3 participants


Before submitting pull request, please check that every commit:

  • Has proper Signed-Off-By
  • Has commit message which describes it
  • Is needed on it's own, if you have just minor fixes to previous commits, you can squash them
  • Any new functionality is covered by tests

MySQL allows precision to be specified for DATETIME, TIME type fields too, we should allow it to be specified.


Fix #12814

devenbansod added some commits Dec 15, 2016
@devenbansod devenbansod MySQL allows precision to be specified for DATETIME, TIME type fields…
… too

Fix #12814

Ref :

Signed-off-by: Deven Bansod <>
@devenbansod devenbansod ChangeLog for #12814
Signed-off-by: Deven Bansod <>

Current coverage is 50.15% (diff: 100%)

No coverage report found for QA_4_6 at 128b027.

Powered by Codecov. Last update 128b027...967755a

@nijel nijel self-assigned this Dec 20, 2016
@nijel nijel added this to the 4.6.6 milestone Dec 20, 2016
@nijel nijel merged commit 967755a into phpmyadmin:QA_4_6 Dec 20, 2016

4 checks passed

codecov/patch Coverage not affected.
codecov/project 50.15% (+0.00%) compared to 96350a7
continuous-integration/travis-ci/pr The Travis CI build passed
coverage/coveralls First build on QA_4_6 at 49.744%
nijel commented Dec 20, 2016

Merged, thanks for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment