1. 23 1月, 2001 1 次提交
  2. 22 1月, 2001 2 次提交
  3. 21 1月, 2001 8 次提交
  4. 20 1月, 2001 12 次提交
  5. 19 1月, 2001 13 次提交
  6. 18 1月, 2001 4 次提交
    • P
      Thu Jan 18 12:24:00 GMT 2001 peter@retep.org.uk · 45b5d792
      Peter Mount 提交于
              - These methods in org.postgresql.jdbc2.ResultSet are now implemented:
                  getBigDecimal(int) ie: without a scale (why did this get missed?)
                  getBlob(int)
                  getCharacterStream(int)
                  getConcurrency()
                  getDate(int,Calendar)
                  getFetchDirection()
                  getFetchSize()
                  getTime(int,Calendar)
                  getTimestamp(int,Calendar)
                  getType()
                NB: Where int represents the column name, the associated version
                    taking a String were already implemented by calling the int
                    version.
              - These methods no longer throw the not implemented but the new noupdate
                error. This is in preparation for the Updateable ResultSet support
                which will overide these methods by extending the existing class to
                implement that functionality, but needed to show something other than
                notimplemented:
                  cancelRowUpdates()
                  deleteRow()
              - Added new error message into errors.properties "postgresql.noupdate"
                This is used by jdbc2.ResultSet when an update method is called and
                the ResultSet is not updateable. A new method notUpdateable() has been
                added to that class to throw this exception, keeping the binary size
                down.
              - Added new error message into errors.properties "postgresql.psqlnotimp"
                This is used instead of unimplemented when it's a feature in the
                backend that is preventing this method from being implemented.
              - Removed getKeysetSize() as its not part of the ResultSet API
      
      Thu Jan 18 09:46:00 GMT 2001 peter@retep.org.uk
              - Applied modified patch from Richard Bullington-McGuire
                <rbulling@microstate.com>. I had to modify it as some of the code
                patched now exists in different classes, and some of it actually
                patched obsolete code.
      
      Wed Jan 17 10:19:00 GMT 2001 peter@retep.org.uk
              - Updated Implementation to include both ANT & JBuilder
              - Updated README to reflect the changes since 7.0
      	- Created jdbc.jpr file which allows JBuilder to be used to edit the
                source. JBuilder _CAN_NOT_ be used to compile. You must use ANT for
                that. It's only to allow JBuilders syntax checking to improve the
                drivers source. Refer to Implementation for more details
      45b5d792
    • H
      Fix some leaks(was my fault). · 89ac6439
      Hiroshi Inoue 提交于
      89ac6439
    • T
      Fix up "Postgres-style" time interval representation when fields have · 6acdebbd
      Thomas G. Lockhart 提交于
       mixed-signs. Previous effort left way too many minus signs, and was at
       least as broken as the one before that :(
      Clean up "ISO-style" time interval representation to omit zero fields if
       there is at least one non-zero field. Supress some leading plus signs
       when not necessary for clarity.
      Replace every #ifdef __CYGWIN__ block with a cleaner TIMEZONE_GLOBAL macro
       defined in datetime.h.
      6acdebbd
    • T
      Fix performance issue with qualifications on VIEWs: outer query should · b06fbc7a
      Tom Lane 提交于
      try to push restrictions on the view down into the view subquery,
      so that they can become indexscan quals or what-have-you rather than
      being applied at the top level of the subquery.  7.0 and before were
      able to do this, though in a much klugier way, and I'd hate to have
      anyone complaining that 7.1 is stupider than 7.0 ...
      b06fbc7a