1. 25 Jan, 2001 2 commits
    • Bruce Momjian's avatar
      Further to the previous ODBC patches I posted today, I found a couple of · 40203e4f
      Bruce Momjian authored
      problems with char array sizes having set a couple of constants to 0 for
      unlimited query length and row length. This additional patch cleans those
      problems up by defining a new constant (STD_STATEMENT_LEN) to 65536 and
      using that in place of MAX_STATEMENT_LEN.
      
      Another constant (MAX_MESSAGE_LEN) was defined as 2*BLCKSZ, but is now
      65536. This is used to define the length of the message buffer in a number
      of places and as I understand it (probably not that well!) therefore also
      places a limit on the query length. Fixing this properly is beyond my
      capabilities but 65536 should hopefully be large enough for most people.
      
      Apologies for being over-enthusiastic and posting 3 patches in one day
      rather than 1 better tested one!
      
      Regards,
      
      Dave Page
      40203e4f
    • Bruce Momjian's avatar
      I decided to give this a go after all :-) The attached patch does the · be127684
      Bruce Momjian authored
      following but it does *not* check whether the user is connected to
      PostgreSQL 7.0.x or 7.1 first (as would be required for some of the
      features) - the driver doesn't do this at all afaik and it's beyond my
      capabilities to implement such checking in code that doesn't look like it
      was written by my 1 year old daughter!
      
      1) The driver now reports no maximum query length (SQL_MAX_QUERY_SIZE).
      2) The driver now reports no maximum row length (SQL_MAX_ROW_SIZE).
      3) The driver now reports that Outer Joins are supported (SQL_OUTER_JOINS),
      but still does not report oj capabilities (SQL_OJ_CAPABILITIES).
      4) The version number has been incremented to 7.1.0000 in psqlodbc.h *and*
      psqlodbc.rc
      
      
      Regards,
      
      Dave Page
      be127684
  2. 11 Dec, 2000 2 commits
  3. 10 Dec, 2000 1 commit
  4. 08 Jun, 2000 2 commits
  5. 27 May, 2000 1 commit
  6. 17 May, 2000 1 commit
  7. 16 May, 2000 1 commit
    • Bruce Momjian's avatar
      Several compilation and run-time problems occur when building on SGI · a47e20b0
      Bruce Momjian authored
      IRIX systems using the native compilers.  A summary is:
      - Various files use "//" as a comment delimiter in c files.
      - Problems caused by assuming "char" is signed.
        cash.in: building -signed the rules regression test fails as described
          in FAQ_QNX4.  If CHAR_MAX is "255U" then ((signed char)CHAR_MAX) is -1.
        postmaster.c: random number regression test failed without this change.
      - Some generic build issues and warning message cleanup.
      
      David Kaelbling
      a47e20b0
  8. 28 Feb, 2000 1 commit
  9. 30 Jan, 2000 1 commit
  10. 30 Nov, 1999 1 commit
  11. 03 Sep, 1999 1 commit
  12. 13 May, 1999 1 commit
  13. 03 May, 1999 1 commit
    • Bruce Momjian's avatar
      here are some patches for 6.5.0 which I already submitted but have never · 210055ad
      Bruce Momjian authored
      been applied. The patches are in the .tar.gz attachment at the end:
      
      varchar-array.patch     this patch adds support for arrays of bpchar() and
                              varchar(), which where always missing from postgres.
      
                              These datatypes can be used to replace the _char4,
                              _char8, etc., which were dropped some time ago.
      
      block-size.patch        this patch fixes many errors in the parser and other
                              program which happen with very large query statements
                              (> 8K) when using a page size larger than 8192.
      
                              This patch is needed if you want to submit queries
                              larger than 8K. Postgres supports tuples up to 32K
                              but you can't insert them because you can't submit
                              queries larger than 8K. My patch fixes this problem.
      
                              The patch also replaces all the occurrences of `8192'
                              and `1<<13' in the sources with the proper constants
                              defined in include files. You should now never find
                              8192 hardwired in C code, just to make code clearer.
      
      
      --
      Massimo Dal Zotto
      210055ad
  14. 08 Jan, 1999 1 commit
  15. 06 Jan, 1999 1 commit
  16. 31 Dec, 1998 1 commit
  17. 29 Dec, 1998 1 commit
  18. 11 Nov, 1998 1 commit
    • Byron Nikolaidis's avatar
      · 87225ca3
      Byron Nikolaidis authored
      Update for version 06-40-0001
      87225ca3
  19. 06 Oct, 1998 1 commit
    • Thomas G. Lockhart's avatar
      Update source code to Byron's v6.30.0250 sources plus minor cleanup · 1eab86e2
      Thomas G. Lockhart authored
       to get rid of unused variables.
      Get clean compile on Linux (Thomas and Gerald).
      Implement autoconf/configure for standalone builds and use the existing
       autoconf/configure system when in the Postgres source tree.
      Code tests and functions with ApplixWare-4.4.1beta on a Linux box.
      Changes should be backward compatible with WIN32 but still needs testing.
      1eab86e2
  20. 22 Jul, 1998 1 commit
  21. 16 Jun, 1998 1 commit
  22. 08 Jun, 1998 1 commit
  23. 03 Jun, 1998 1 commit
  24. 13 Apr, 1998 1 commit