- 16 May, 2001 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 14 May, 2001 1 commit
-
-
Bruce Momjian authored
-
- 08 May, 2001 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 27 Mar, 2001 1 commit
-
-
Bruce Momjian authored
-
- 23 Mar, 2001 1 commit
-
-
Bruce Momjian authored
-
- 22 Mar, 2001 1 commit
-
-
Bruce Momjian authored
-
- 10 Mar, 2001 1 commit
-
-
Hiroshi Inoue authored
2)Fix some memory leaks. 3)Change some bogus error messages.
-
- 14 Feb, 2001 1 commit
-
-
Bruce Momjian authored
protocol. I have left in Tom's SOCK_get_next_byte() fix, and the new win32.mak file addition. I have also left in the 'X' connection close fix.
-
- 11 Feb, 2001 4 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
1) Tidies up the Datasource Dialogue now the version options are gone. 2) Tidies a comment in info.c. 3) Increments all version numbers to 07.01.0003 to take account of recent revisions. Regards, Dave Page
-
- 10 Feb, 2001 3 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
weren't the master source. We are now, and it really needs it.
-
Bruce Momjian authored
-
- 06 Feb, 2001 1 commit
-
-
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>>
-
- 26 Jan, 2001 1 commit
-
-
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
-
- 25 Jan, 2001 3 commits
-
-
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
-
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
-
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
-
- 23 Jan, 2001 1 commit
-
-
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
-
- 11 Dec, 2000 1 commit
-
-
Bruce Momjian authored
not match.
-
- 10 Dec, 2000 1 commit
-
-
Bruce Momjian authored
return foreign key information based on the pg_trigger system table. I have tested the patch with (what I believe) is all possible primary/foreign key combinations -- however I may have missed some, so if anyone feels like taking the patch for a test drive, here are some useful links: Michael Fork
-
- 03 Dec, 2000 1 commit
-
-
Tom Lane authored
values, whether the local char type is signed or not. This is necessary for portability. Per discussion on pghackers around 9/16/00.
-
- 24 Oct, 2000 1 commit
-
-
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!
-
- 29 Aug, 2000 1 commit
-
-
Tom Lane authored
-
- 27 May, 2000 1 commit
-
-
Bruce Momjian authored
-
- 17 May, 2000 1 commit
-
-
Bruce Momjian authored
-
- 16 May, 2000 1 commit
-
-
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
-
- 27 Mar, 2000 1 commit
-
-
Thomas G. Lockhart authored
We still have an internal limit in the ODBC code of 8 columns per key, but this should lay the groundwork for resolving that. Includes reformulated query from Tom Lane.
-
- 21 Mar, 2000 1 commit
-
-
Thomas G. Lockhart authored
Reported by "Tibor Laszlo" <ltibor@mail.tiszanet.hu> and fix suggested by "Hiroshi Inoue" <Inoue@tpf.co.jp>.
-
- 30 Jan, 2000 1 commit
-
-
Byron Nikolaidis authored
Bug fix for LongVarBinary -- begin transaction
-
- 05 Jan, 2000 1 commit
-
-
Bruce Momjian authored
-
- 30 Nov, 1999 1 commit
-
-
Bruce Momjian authored
-
- 03 Sep, 1999 1 commit
-
-
Byron Nikolaidis authored
-
- 03 May, 1999 1 commit
-
-
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
-
- 08 Jan, 1999 1 commit
-
-
Byron Nikolaidis authored
-
- 06 Jan, 1999 1 commit
-
-
Byron Nikolaidis authored
-