1. 24 Aug, 2001 1 commit
  2. 21 Aug, 2001 1 commit
  3. 18 Aug, 2001 1 commit
    • Hiroshi Inoue's avatar
      1) Change all internal SQL function calls from · 0c439e5e
      Hiroshi Inoue authored
         SQLxxxx() to PGAPI_xxxx().
      2) Handle an escaped date/time format as a parameter.
      3) Improve the tuple allocation a little.
      4) The preparation of ODBC 3.0 a little.
      5) Updatable cursors(may be deprecated before long).
      0c439e5e
  4. 27 Jun, 2001 1 commit
  5. 22 Jun, 2001 1 commit
  6. 25 May, 2001 1 commit
  7. 17 May, 2001 1 commit
  8. 16 May, 2001 2 commits
  9. 14 May, 2001 1 commit
  10. 08 May, 2001 2 commits
  11. 27 Mar, 2001 1 commit
  12. 23 Mar, 2001 1 commit
  13. 22 Mar, 2001 1 commit
  14. 10 Mar, 2001 1 commit
  15. 14 Feb, 2001 1 commit
  16. 11 Feb, 2001 4 commits
  17. 10 Feb, 2001 3 commits
  18. 06 Feb, 2001 1 commit
    • Hiroshi Inoue's avatar
      Improved version handling introduced by Dave Page. · 5d08521f
      Hiroshi Inoue authored
      The driver version is 07.01.0002 now.
      1) initialized pg_version by DSN's protocol info
         so that we could always use pg_version info
         once a connection is established (pg_version()
         didn't exist before 6.4). PROTOCOL_XX() macros
         are removed(except from connection.[ch]).
      2) provided a few macros to encapsulate connection's
         version info and replaced existent comparison
         stuff by those macros.
      3) change SQLTables() so that 7.1 servers could show
         views.
      
      
      In addtion, the following patch from Dave Page is applied.
      
        This patch fixes a bug in SQLGetInfo for SQL_DBMS_VER which corrupted the
        driver version string. The driver version number has also been incremented
        to 07.01.0002.
      
        Regards, Dave. <<odbc.diff>>
      5d08521f
  19. 26 Jan, 2001 1 commit
    • Bruce Momjian's avatar
      odbc1.diff changes the text on the Protocol Radio buttons on the driver · 5a832218
      Bruce Momjian authored
      dialogue from '6.4/6.5' to '6.5+' and removes some C++ comments from
      resource.h (which VC++ insists on putting there).
      
      odbc2.diff adds code to query the PostgreSQL version upon connection. This
      is then used to determine what values to return for from SQLGetInfo for
      SQL_DBMS_VER, SQL_MAX_ROW_SIZE, SQL_MAX_STATEMENT_LEN, SQL_OJ_CAPABILITIES
      and SQL_OUTER_JOINS. The version string as returned by SELECT vERSION() (as
      a char array) and the major.minor version number (as a flost) have been
      added to the ConnectionClass structure.
      
      Dave Page
      5a832218
  20. 25 Jan, 2001 3 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
      > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] · 0e968ee7
      Bruce Momjian authored
      > Sent: 24 January 2001 16:51
      > To: Dave Page
      > Subject: Re: [PATCHES] ODBC Patch for OJs/Large Querys & Rows
      >
      >
      > > SQL_OJ_LEFT = Left outer joins are supported.
      >
      > Yes.
      <snip>
      
      In addition to my earlier patch, this one adds support for SQLGetInfo
      SQL_OJ_CAPABILITIES to the ODBC driver.
      
      Dave Page
      0e968ee7
    • 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
  21. 23 Jan, 2001 1 commit
    • Bruce Momjian's avatar
      Subject: Bug in SQLForeignKeys() · edfca4b9
      Bruce Momjian authored
      Query used for checking foreign key triggers
      returns too many results when there're more than one foreign
      key in a table. It happens because only table's oid is used to
      link between pg_trigger with INSERT check and pg_trigger with
      UPDATE/DELETE check.
      
      I think there should be enough to add following conditions
      into WHERE clause of that query:
              AND     pt.tgconstrname = pg_trigger.tgconstrname
              AND     pt.tgconstrname = pg_trigger_1.tgconstrname
      
      /Constantin
      edfca4b9
  22. 11 Dec, 2000 1 commit
  23. 10 Dec, 2000 1 commit
  24. 03 Dec, 2000 1 commit
  25. 24 Oct, 2000 1 commit
    • Tom Lane's avatar
      Major overhaul of large-object implementation, by Denis Perchine with · 4f44aa04
      Tom Lane authored
      kibitzing from Tom Lane.  Large objects are now all stored in a single
      system relation "pg_largeobject" --- no more xinv or xinx files, no more
      relkind 'l'.  This should offer substantial performance improvement for
      large numbers of LOs, since there won't be directory bloat anymore.
      It'll also fix problems like running out of locktable space when you
      access thousands of LOs in one transaction.
      Also clean up cruft in read/write routines.  LOs with "holes" in them
      (never-written byte ranges) now work just like Unix files with holes do:
      a hole reads as zeroes but doesn't occupy storage space.
      INITDB forced!
      4f44aa04
  26. 29 Aug, 2000 1 commit
  27. 27 May, 2000 1 commit
  28. 17 May, 2000 1 commit
  29. 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
  30. 27 Mar, 2000 1 commit
  31. 21 Mar, 2000 1 commit