1. 22 Sep, 2001 1 commit
    • Peter Eisentraut's avatar
      Provide some initial support for building the ODBC driver for · 364a7ebe
      Peter Eisentraut authored
      an already installed iODBC or unixODBC driver manager.  In particular,
      use the include files provided by the driver manager over our own,
      and use the odbcinst library of the driver manager rather than gpps.c.
      
      Migrate portability sections common to several files into psqlodbc.h.
      364a7ebe
  2. 08 Sep, 2001 1 commit
  3. 07 Sep, 2001 1 commit
  4. 24 Aug, 2001 1 commit
  5. 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
  6. 27 Jun, 2001 1 commit
  7. 17 May, 2001 1 commit
  8. 01 May, 2001 1 commit
  9. 27 Mar, 2001 1 commit
  10. 22 Mar, 2001 1 commit
  11. 16 Mar, 2001 1 commit
    • Hiroshi Inoue's avatar
      Add multibyte support. · 9242e6c0
      Hiroshi Inoue authored
      	Provide an extenisible scheme of encoding conversion.
      	As the first step, SJIS and BIG5 are supported.
      	From now on multibyte people would be happy to use
      	this psqlodbc driver.
      
      Eiji Tokuya e-tokuya@mail.sankyo-unyu.co.jp
      9242e6c0
  12. 15 Feb, 2001 1 commit
    • Hiroshi Inoue's avatar
      1) Change transaction boundary in autocommit off mode · 462c1321
      Hiroshi Inoue authored
         per recent discussion in pgsql-odbc. Now SELECT is
         a boundary but VACUUM isn't.
      2) Put back the error handling behavior. When elog(ERROR)
         was detected the driver automatically issue "ABORT"
         if a transaction is in progress.
      3) Driver version is 7.01.0003(Dave already set it but
         it was put back).
      462c1321
  13. 14 Feb, 2001 1 commit
  14. 11 Feb, 2001 4 commits
  15. 10 Feb, 2001 2 commits
  16. 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
  17. 26 Jan, 2001 2 commits
    • 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
    • Tom Lane's avatar
      7edafafd
  18. 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
  19. 11 Dec, 2000 2 commits
  20. 10 Dec, 2000 1 commit
  21. 08 Jun, 2000 2 commits
  22. 27 May, 2000 1 commit
  23. 17 May, 2000 1 commit
  24. 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
  25. 28 Feb, 2000 1 commit
  26. 30 Jan, 2000 1 commit
  27. 30 Nov, 1999 1 commit
  28. 03 Sep, 1999 1 commit
  29. 13 May, 1999 1 commit
  30. 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
  31. 08 Jan, 1999 1 commit
  32. 06 Jan, 1999 1 commit