[COMMITTERS] pgsql: Fixed bug 2330: Wrong error code in case of a duplicate key
Log Message: --- Fixed bug 2330: Wrong error code in case of a duplicate key Tags: REL8_1_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/ecpglib: error.c (r1.11 -> r1.11.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ecpglib/error.c.diff?r1=1.11&r2=1.11.2.1) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: Fixed bug 2330: Wrong error code in case of a duplicate key
Log Message: --- Fixed bug 2330: Wrong error code in case of a duplicate key Tags: REL8_0_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/ecpglib: error.c (r1.10 -> r1.10.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ecpglib/error.c.diff?r1=1.10&r2=1.10.4.1) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fixed bug 2330: Wrong error code in case of a duplicate key
Log Message: --- Fixed bug 2330: Wrong error code in case of a duplicate key Tags: REL7_4_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/ecpglib: error.c (r1.9 -> r1.9.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ecpglib/error.c.diff?r1=1.9&r2=1.9.2.1) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] python - ip: New Directory
Update of /cvsroot/python/ip/test In directory pgfoundry.org:/tmp/cvs-serv94186/test Log Message: Directory /cvsroot/python/ip/test added to the repository ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] python - fe: Use Green Trunk's new base functionality in Connectors and
Log Message: --- Use Green Trunk's new base functionality in Connectors and Fittings. Also, get rid of the "first connection" when instantiating Connectors. This provided some convenience by answering some questions prior to actually making a real connection, but the overhead of that first connection creates is fantastically undesirable, so displace the solution resolution to the actual first connection made by the user. While this has the effect of allowing "invalid" Connectors, it is unlikely to be a impedance on any application--unlike fc. Additionally, it provides the user with the ability to correct connector arguments without being forced to create another connector. Modified Files: -- fe/src: abstract.py (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/abstract.py.diff?r1=1.2&r2=1.3) dbapi2.py (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/dbapi2.py.diff?r1=1.1&r2=1.2) tracenull.py (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.16&r2=1.17) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - ip: Implement some common code in Connector and Fitting
Log Message: --- Implement some common code in Connector and Fitting classes. These were more abstract, but some common functionality could be implemented here, so do so. In particular, the way in which Connectors are instantiated is a bit difficult, so avoid the headaches of duplication by placing them here. Also, introduce the idea of adaption for Interface classes. This provides the ability to layer interfaces on already established connections, instead of requiring a new Connector to be used. Modified Files: -- ip/src: abstract.py (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ip/src/abstract.py.diff?r1=1.2&r2=1.3) Added Files: --- ip/test: abstract.py (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ip/test/abstract.py?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix a few places that were checking for the return value of
Log Message: --- Fix a few places that were checking for the return value of palloc() to be non-NULL: palloc() ereports on OOM, so we can safely assume it returns a valid pointer. Modified Files: -- pgsql/contrib/chkpass: chkpass.c (r1.14 -> r1.15) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/chkpass/chkpass.c.diff?r1=1.14&r2=1.15) pgsql/contrib/fuzzystrmatch: fuzzystrmatch.c (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/fuzzystrmatch/fuzzystrmatch.c.diff?r1=1.19&r2=1.20) pgsql/src/backend/utils/adt: cash.c (r1.66 -> r1.67) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/cash.c.diff?r1=1.66&r2=1.67) pgsql/src/pl/plperl: SPI.xs (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/SPI.xs.diff?r1=1.19&r2=1.20) plperl.c (r1.106 -> r1.107) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r1=1.106&r2=1.107) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] python - fe: Use sorted items as key.
Log Message: --- Use sorted items as key. (Using the str() of seemed fragile.) Modified Files: -- fe/src: dbapi2.py (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/dbapi2.py.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - ex: Give AbortTransaction the ability to return an object.
Log Message: --- Give AbortTransaction the ability to return an object. Also, rename NO_DATA to NO_DATA_WARNING as it is a warning. Make prime.Error inherit from StandardError and prime.Exception. Implement Warning.__str__. Modified Files: -- ex/src: code.py (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ex/src/code.py.diff?r1=1.6&r2=1.7) prime.py (r1.9 -> r1.10) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ex/src/prime.py.diff?r1=1.9&r2=1.10) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] python - fe: Use AbortTransaction.returning in Transact.
Log Message: --- Use AbortTransaction.returning in Transact. [Test for it as well] Modified Files: -- fe/src: tracenull.py (r1.17 -> r1.18) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.17&r2=1.18) fe/test: tracenull.py (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/test/tracenull.py.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] python - ip: Content update.
Log Message: --- Content update. Remove the Relation and Namespace section until a better idea of what they should be is realized. Add and change some mechanics to Query, Function, Portal, and Transaction. Remove wording requiring that the Query attribute should be a type as it was an unnecessary limitation. Remove wording requiring that Connectors validate the capacity to make a connection. An undesirable limitation that aided in resolving some questions about the database, but ultimately was more of an impedance. Modified Files: -- ip: spec.xml (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ip/spec.xml.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] python - ex: Use the codename for the package name.
Log Message: --- Use the codename for the package name. Modified Files: -- ex: setup.py (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ex/setup.py.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] python - fe: Fix break from string to list use in connection dictionary.
Log Message: --- Fix break from string to list use in connection dictionary. List objects aren't hashable, so make it a tuple. Modified Files: -- fe/src: dbapi2.py (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/dbapi2.py.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] python - pq: Let the user handle the following Ready message.
Log Message: --- Let the user handle the following Ready message. Also, the transaction is fatal if an exception(_exc_info exists) occurred and the invalid_message was not an error message. Modified Files: -- pq/src: client3.py (r1.20 -> r1.21) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.20&r2=1.21) ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] python - fe: Don't send sync if the transaction is Querying or Function.
Log Message: --- Don't send sync if the transaction is Querying or Function. Modified Files: -- fe/src: tracenull.py (r1.18 -> r1.19) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/fe/src/tracenull.py.diff?r1=1.18&r2=1.19) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] orafce - orafce: dbms_pipe completed
Log Message: --- dbms_pipe completed Modified Files: -- orafce: Makefile (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/Makefile.diff?r1=1.6&r2=1.7) README.orafunc (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/README.orafunc.diff?r1=1.10&r2=1.11) orafunc.h (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/orafunc.h.diff?r1=1.1&r2=1.2) orafunc.sql.in (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/orafunc.sql.in.diff?r1=1.12&r2=1.13) pipe.c (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/pipe.c.diff?r1=1.4&r2=1.5) shmmc.c (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/shmmc.c.diff?r1=1.2&r2=1.3) shmmc.h (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/shmmc.h.diff?r1=1.2&r2=1.3) orafce/sql: dbms_pipe.sql (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/sql/dbms_pipe.sql.diff?r1=1.1&r2=1.2) orafunc.sql (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/sql/orafunc.sql.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
