src/share/classes/java/sql/BatchUpdateException.java

*** 1,7 ****
  /*
!  * Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
   * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
   *
   * This code is free software; you can redistribute it and/or modify it
   * under the terms of the GNU General Public License version 2 only, as
   * published by the Free Software Foundation.  Oracle designates this
--- 1,7 ----
  /*
!  * Copyright (c) 1998, 2014, Oracle and/or its affiliates. All rights reserved.
   * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
   *
   * This code is free software; you can redistribute it and/or modify it
   * under the terms of the GNU General Public License version 2 only, as
   * published by the Free Software Foundation.  Oracle designates this
*** 477,494 ****
     * Starting with Java SE 8, JDBC has added support for returning an update
     * count > Integer.MAX_VALUE.  Because of this the following changes were made
     * to BatchUpdateException:
     * <ul>
     * <li>Add field longUpdateCounts</li>
!    * <li>Add Constructorr which takes long[] for update counts</li>
     * <li>Add getLargeUpdateCounts method</li>
     * </ul>
     * When any of the constructors are called, the int[] and long[] updateCount
     * fields are populated by copying the one array to each other.
     *
     * As the JDBC driver passes in the updateCounts, there has always been the
!    * possiblity for overflow and BatchUpdateException does not need to account
     * for that, it simply copies the arrays.
     *
     * JDBC drivers should always use the constructor that specifies long[] and
     * JDBC application developers should call getLargeUpdateCounts.
     */
--- 477,494 ----
     * Starting with Java SE 8, JDBC has added support for returning an update
     * count > Integer.MAX_VALUE.  Because of this the following changes were made
     * to BatchUpdateException:
     * <ul>
     * <li>Add field longUpdateCounts</li>
!    * <li>Add Constructor which takes long[] for update counts</li>
     * <li>Add getLargeUpdateCounts method</li>
     * </ul>
     * When any of the constructors are called, the int[] and long[] updateCount
     * fields are populated by copying the one array to each other.
     *
     * As the JDBC driver passes in the updateCounts, there has always been the
!    * possibility for overflow and BatchUpdateException does not need to account
     * for that, it simply copies the arrays.
     *
     * JDBC drivers should always use the constructor that specifies long[] and
     * JDBC application developers should call getLargeUpdateCounts.
     */