fix: correct SmallDateTime upper bound range

[rockymadden]

Before submitting a PR :

1. Ensure your fork is created from master branch of the repository.
2. Run npm install in the root folder.
3. After bug fix/code change, ensure all the existing tests and new tests (if any) pass (npm run-script test-all). During development, to run individual test use node_modules/nodeunit test/<test_file.js> -t <test_name>.
4. Build the driver (npm run build).
5. Run eslint and flow typechecker (npm run lint).
6. Run commitlint (node_modules/.bin/commitlint --from origin/master --to HEAD). Refer commit conventions and commit rules.

Thank you for Contributing!

[MichaelSun90]

Thanks for catching this and puttying in the effort for raising this PR. I just had a comment for remove an unnecessary test case, and it should be good to go. 🙇

[MichaelSun90]

Sorry, I may put my pervious comment at a confusing line. I added new comment, and hope it will clear things up.

[MichaelSun90]

Sorry, Maybe I was being confusing on this. I mean that the test case that test against May 7, 2079 can be removed since it this date is a valid smalldatetime value. Your original modification that change June 1, 2079 to June 7, 2079 is still a valid modification we should keep that.
Basically this test will looks like this:

describe('.validate', function() {
    it.only('returns a TypeError for dates that are out of range', function() {
      assert.throws(() => {
        TYPES.SmallDateTime.validate(new Date('Dec 31, 1889'));
      }, TypeError, 'Out of range.');

      assert.throws(() => {
        TYPES.SmallDateTime.validate(new Date('Jan 1, 2080'));
      }, TypeError, 'Out of range.');

      assert.throws(() => {
        TYPES.SmallDateTime.validate(new Date('June 7, 2079'));
      }, TypeError, 'Out of range.');
    });
  });