aboutsummaryrefslogtreecommitdiff
path: root/src/interfaces
Commit message (Collapse)AuthorAge
* Enable IPv6 connections to the server, and add pg_hba.conf IPv6 entriesBruce Momjian2003-01-06
| | | | | | | if the OS supports it. Code will still compile on non-IPv6-aware machines (feature added by Bruce). Nigel Kukard
* Adjust Tcl-related code to compile cleanly with Tcl 8.4 (add const modifiers asTom Lane2002-12-30
| | | | needed). Some desultory const-ification of SPI interface to support this.
* Attached is a patch to provide makefiles, etc. to allow the compilationBruce Momjian2002-12-30
| | | | | | | of the libpq interface static and dynamic libraries with the freely downloadable Borland C++ compiler version 5.5 and/or C++ Builder. Lester Godwin
* Make use of TCL_INCLUDE_SPEC if available (it's new in Tcl 8.4, too badTom Lane2002-12-30
| | | | it took 'em this long to realize it's needed...)
* Add missing slash to python install path.Bruce Momjian2002-12-30
|
* case sensitive updates by Kris JurkaDave Cramer2002-12-23
|
* mike beachy's patch for statement handlingDave Cramer2002-12-20
|
* patch for null table in getPrimaryKeysDave Cramer2002-12-20
|
* pgindent fe-connect.c --- done to make IPv6 patch easier to apply.Bruce Momjian2002-12-19
|
* From the SSL_CTX_new man page:PostgreSQL Daemon2002-12-18
| | | | | | | | | | | | | "SSLv23_method(void), SSLv23_server_method(void), SSLv23_client_method(void) A TLS/SSL connection established with these methods will understand the SSLv2, SSLv3, and TLSv1 protocol. A client will send out SSLv2 client hello messages and will indicate that it also understands SSLv3 and TLSv1. A server will understand SSLv2, SSLv3, and TLSv1 client hello messages. This is the best choice when compatibility is a concern." This will maintain backwards compatibility for those us that don't use TLS connections ...
* Increment libpq major number for 7.3.1 and minor for 7.4.Bruce Momjian2002-12-13
|
* Protect from null param on ecpg disconnect, verified by Roland KarchBruce Momjian2002-12-13
|
* > There is an ugly little problem with the DB wrapper class.Bruce Momjian2002-12-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | > > In pg.py the attributes of DB are defined as being the same as > the attributes of the corresponding pgobject "db", using the following ... > The problem is that the attributes of db (which are read only) > are not static (they are actually function calls to PostgreSQL), > especially "status" and "error", but those attributes are copied > and this is done only once when initializing the DB object. > > So, in effect, only the attribute "db.error" of a DB instance > will be updated, but not the attribute "error". Same with "status". > Don't copy the (read only) attributes of the pgobject to the > DB object, but only the methods, and all of them, like this: > > --------------- change in pg.py ------------------ > # Create convience methods, in a way that is still overridable. > for e in self.db.__methods__: > setattr(self, e, getattr(self.db, e)) > ---------------------------------------------------- > > Furthermore, make an addition to the documentation of the > DB wrapper class (i.e. in pygresql-pg-db.html): > After the sentence "All pgobject methods are included in this class also." > add the following sentence "The pgobject read-only attributes can be > accessed py adding the prefix 'db.' to them." Christoph Zwerschke
* Check SSL_get_error() value SSL_ERROR_SYSCALL to see if SSL_read()Bruce Momjian2002-12-12
| | | | | | returned -1, per SSL_get_error() documentation. Nathan Mueller
* While porting my TPC-C implementation from Oracle, I discovered theBruce Momjian2002-12-12
| | | | | | attached problem with the EXEC SQL COMMIT RELEASE statement. Roland Karch
* patch for getTables to fix problems with backends before 7.3 by Kris JurkaDave Cramer2002-12-11
|
* Mike Beachy's build patch to allow ant builds without makeDave Cramer2002-12-11
|
* Aaron's patch for Pooled ConnectionsDave Cramer2002-12-11
|
* Bump version for 7.3 and 7.4.Bruce Momjian2002-12-11
|
* Add an unnecessary assignment to remove a bogus warning. I checked theD'Arcy J.M. Cain2002-12-10
| | | | | logic carefully and I am sure that the test against n happens after it is assigned to.
* Back out V6 code, caused postmaster startup failure.Bruce Momjian2002-12-06
|
* We have just finished porting the old KAME IPv6 patch over toBruce Momjian2002-12-06
| | | | | | | | | | | postgresql version 7.3, but yea... this patch adds full IPv6 support to postgres. I've tested it out on 7.2.3 and has been running perfectly stable. CREDITS: The KAME Project (Initial patch) Nigel Kukard <nkukard@lbsd.net> Johan Jordaan <johanj@lando.co.za>
* PyGreSQL inserttable patchBruce Momjian2002-12-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ===================== I suggested an improvement of the inserttable in the PyGreSQL interface already in January, but seemingly it was never implemented. I was told this is the right place to get patches in for PyGreSQL, so I'm reposting my patch here. I consider the inserttable methode essential in populating the database because of its benefits in performance compared to insert, so I think this patch is quite essential. The attachment is an improved version of the corresponding pg_inserttable function in pgmodule.c, which fixes the following problems: * The function raised exceptions because PyList_GetItem was used beyond the size of the list. This was checked by comparing the result with NULL, but the exception was not cleaned up, which could result in mysterious errors in the following Python code. Instead of clearing the exception using PyErr_Clear or something like that, I avoided throwing the exception at all by at first requesting the size of the list. Using this opportunity, I also checked the uniformity of the size of the rows passed in the lists/tuples. The function also accepts (and silently ignores) empty lists and sublists. * Python "None" values are now accepted and properly converted to PostgreSQL NULL values * The function now generates an error message in case of a line buffer overflow * It copes with tabulators, newlines and backslashes in strings now * Rewrote the buffer filling code which should now run faster by avoiding unnecessary string copy operations forth and back Christoph Zwerschke
* changed sort of column names to sort by attnum, not attnameDave Cramer2002-12-05
|
* Stamp minor version numbers for 7.4 release.Bruce Momjian2002-12-04
|
* Remove typprtlen from getdescr() as it is not available in 7.3. Return -1 forD'Arcy J.M. Cain2002-12-04
| | | | that field so that existing programs don't break.
* Deal with cases where getpeereid _and_ another creditial method isBruce Momjian2002-12-03
| | | | supported.
* Synced parser with backendMichael Meskes2002-11-27
|
* Add -cmdTuples to tcl interface.Bruce Momjian2002-11-26
|
* I'm sending you a small patch to pgdb.py module. ThisD'Arcy J.M. Cain2002-11-25
| | | | | | | | | | | | | | raises pgdb.DatabaseError when any of the fetch* methods was invoked but previous call to execute* did not produce any result set or no call was issued yet. Also, raises pgdb.NotSupportedError when .nextset() is invoked, instead of NameError. This behaviour complies with DB-API 2.0. Thanks for your work! Timur Irmatov.
* Change the pkey method so that the caller can optionally set the dictionaryD'Arcy J.M. Cain2002-11-25
| | | | | | | | | used for the primary key lookup. This will prevent a database lookup for each connection object that gets created. This could be a significant optimization on a busy system. Similarly, the get_attnames method allows for the attributes dictionary to be installed directly.
* Change the debug variable to allow better control by the caller over howD'Arcy J.M. Cain2002-11-25
| | | | | | | | | | | | | debug output is managed. The user can continue to use the current method of passing a formatting string to have a replacement done and output will be sent to the standard output exactly as it did before. In addition they can set it to a file object, sys.stderr for example, and the query string will be printed to it. Thay can also set it to a method (function) and the query string will be passed to that method giving them the maximum flexibility to do whatever they want with the query string. I will be working with the PyGreSQL documentation shortly and at that time will properly document this feature.
* This patch implements FOR EACH STATEMENT triggers, per my email toBruce Momjian2002-11-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -hackers a couple days ago. Notes/caveats: - added regression tests for the new functionality, all regression tests pass on my machine - added pg_dump support - updated PL/PgSQL to support per-statement triggers; didn't look at the other procedural languages. - there's (even) more code duplication in trigger.c than there was previously. Any suggestions on how to refactor the ExecXXXTriggers() functions to reuse more code would be welcome -- I took a brief look at it, but couldn't see an easy way to do it (there are several subtly-different versions of the code in question) - updated the documentation. I also took the liberty of removing a big chunk of duplicated syntax documentation in the Programmer's Guide on triggers, and moving that information to the CREATE TRIGGER reference page. - I also included some spelling fixes and similar small cleanups I noticed while making the changes. If you'd like me to split those into a separate patch, let me know. Neil Conway
* Fix a dumb cut and paste error from my last commit and update some of theBarry Lind2002-11-20
| | | | | | | | jdbc3 metadata responses Modified Files: jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java jdbc/org/postgresql/jdbc3/AbstractJdbc3DatabaseMetaData.java
* Fixed bug reported by Marko Strukelj and Keith Wannamaker. Using executeBatchBarry Lind2002-11-20
| | | | | | | | | | | | | on a preparedStatement would reset the prepared statment causing subsequent uses of the preparedStatement to fail (i.e. the following series of calls would fail: addBatch() executeBatch() addBatch() executBatch()). This is a regression from 7.2 where this worked correctly. The regression test has also been modified to explicitly test for this case. Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java
* Synced parser.Michael Meskes2002-11-15
|
* Applied patch submitted by Mats Lofkvist fixing serious threading problem ↵Barry Lind2002-11-14
| | | | | | | | | | | | | | | introduced in beta3. Fixed bug with using setNull()(or setXXX(x, null)) and serverside prepare statements. Improved error message when using a connection object that has already been closed. Modified Files: jdbc/org/postgresql/errors.properties jdbc/org/postgresql/core/Encoding.java jdbc/org/postgresql/core/QueryExecutor.java jdbc/org/postgresql/jdbc1/AbstractJdbc1Connection.java jdbc/org/postgresql/jdbc1/AbstractJdbc1Statement.java
* Fixes bug where join to pg_description was incorrect. Also modifies theBarry Lind2002-11-11
| | | | | | | | regression test to test for this case. Patch submitted by Kris Jurka. Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java jdbc/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java
* I just discovered, that there is missing a const when passing a bufferBruce Momjian2002-11-10
| | | | | | | to PQescapeBytea and PQunescapeBytea. I fixed it and tried to create a usable diff (I'm not so familar to diff). Tommi M?kitalo
* Remove inappropriate inclusions of OpenSSL internal header e_os.h,Tom Lane2002-11-07
| | | | | as well as unnecessary (and incorrect on Windows) assignments to errno/SOCK_ERRNO.
* Synced parser one more time.Michael Meskes2002-11-07
|
* Remove no-longer-needed inclusions to improve backward compatibilityTom Lane2002-11-07
| | | | with older bison versions.
* Fix inclusion order, per Andreas.Tom Lane2002-11-04
|
* Applied two patches from Kris Jurka.Barry Lind2002-11-04
| | | | | | | | | | | | | | - First fixes a problem with a recent patch allowing setNull on updateable resultsets - Second removed toLower() calls on database object names. Leave it to the caller to correctly pass lower, upper or mixed case. The driver already has methods that the caller can use to determine that postgres stores identifiers in lowercase. (unless the identifier was quoted when created). Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java
* Arrange to compile flex output files as inclusions into other filesTom Lane2002-11-01
| | | | | | | | (usually bison output files), not as standalone files. This hack works around flex's insistence on including <stdio.h> before we are able to include postgres.h; postgres.h will already be read before the compiler starts to read the flex output file. Needed for largefile support on some platforms.
* Return something meaningful for Statement.getFetchSize(). Previously we wereBarry Lind2002-10-30
| | | | | | | returning an exception when this method was called. Modified Files: jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java
* Patch submitted by Kris Jurka to fix arrayindexoutofbounds exception causedBarry Lind2002-10-25
| | | | | | | by improper array initialization. Modified Files: jdbc/org/postgresql/jdbc1/AbstractJdbc1DatabaseMetaData.java
* Code review for connection timeout patch. Avoid unportable assumptionTom Lane2002-10-24
| | | | | | that tv_sec is signed; return a useful error message on timeout failure; honor PGCONNECT_TIMEOUT environment variable in PQsetdbLogin; make code obey documentation statement that timeout=0 means no timeout.
* Add guards against double inclusion.Peter Eisentraut2002-10-21
|
* Translation updatesPeter Eisentraut2002-10-21
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-18 05:16:56 +0000