aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Thanks for your feedback (and patience). Enclosed is my thirdBruce Momjian2001-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | attempt at a patch to 7.1.2 to support Array. [I think I've solved the mangled patch problem. Hotmail seems to try to format the text file, so gzipping it should solve this problem.] In this patch I've incorporated Barry's feedback. Specifically: 1) OIDs are no longer hard-coded into Array.java. In order to support this change I added a getOID(String) method to Field.java which receives a PostgreSQL field type and returns a value from java.sql.Types. I couldn't get away from using OIDs altogether because the JDBC spec for Array specifies that some methods return a ResultSet. This requires I construct Field objects, which means I need OIDs. At least this approach doesn't hard code these values. A Hashtable cache has been added to Field so that an SQL lookup isn't necessary (following the model already in Field.java). 2) Rewired the base formatting code in ResultSet.java to use 'to' methods, which are then exposed as static methods in ResultSet. These methods are used in Array to format the data without duplications in the code. 3) Artifact call to first() in ResultSet.getArray() removed. Greg Zoller
* Attached is the patch requested by Tom Lane (see below). ItBruce Momjian2001-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | includes two changes in the JDBC driver: 1) When connected to a backend >= 7.2: use obj_description() and col_description() instead of direct access to pg_description. 2) In DatabaseMetaData.getTables()/getColumns()/getProcedures(): when there is no comment on the object, return null in the REMARKS column of the ResultSet, instead of the default string "no remarks". Change 2 first appeared as a side-effect of change 1, but it is actually more compliant with the JDBC spec: "String object containing an explanatory comment on the table/column/procedure, which may be null". The default string "no remarks" was strictly speaking incorrect, as it could not be distinguished from a real user comment "no remarks". So I removed the default string completely. Change 2 might break existing code that doesn't follow the JDBC spec and isn't prepared to handle a null in the REMARKS column of getTables()/getColumns()/getProcedures. Patch tested with jdbc2 against both a 7.1 and a CVS tip backend. I did not have a jdbc1 environment to build and test with, but since the touched code is identical in jdbc1 and jdbc2 I don't foresee any problems. Regards, Ren? Pijlman
* Force crypt() salt to be null-terminated.Bruce Momjian2001-08-17
|
* Add 4-byte MD5 salt.Bruce Momjian2001-08-17
|
* geo_distance function needs to be marked strict.Tom Lane2001-08-16
| | | | From Mark Stosberg.
* Update list of files to update.Bruce Momjian2001-08-16
|
* Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-typeTom Lane2001-08-16
| | | | | | | | has an alias SERIAL4 and a sister SERIAL8. SERIAL8 is just the same except the created column is type int8 not int4. initdb forced. Note this also breaks any chance of pg_upgrade from 7.1, unless we hack up pg_upgrade to drop and recreate sequences. (Which is not out of the question, but I don't wanna do it.)
* Add new MD5 pg_hba.conf keyword. Prevent fallback to crypt.Bruce Momjian2001-08-16
|
* This patch fixes the well-known but unfixed bug that fetchone() always returnsBruce Momjian2001-08-16
| | | | | | | the first result in the DB-API compliant wrapper. It turned out that the bug was way down in the C code. Gerhard Häring
* Fix typo. pg_dump -B --> pg_dump -bTatsuo Ishii2001-08-16
|
* Remove protocol version change. Try MD5 first, then crypt() on all clients.Bruce Momjian2001-08-16
|
* Use malloc/palloc as appropriate.Bruce Momjian2001-08-15
|
* Move md5.h contents to crypt.h.Bruce Momjian2001-08-15
|
* Remove unneeded patch.Bruce Momjian2001-08-15
|
* Remove UNDO dicussion. It was inconclusive, and too large.Bruce Momjian2001-08-15
|
* Just a test.Bruce Momjian2001-08-15
|
* update.Bruce Momjian2001-08-15
|
* updateBruce Momjian2001-08-15
|
* updateBruce Momjian2001-08-15
|
* Add new files.Bruce Momjian2001-08-15
|
* Use MD5 for wire protocol encryption for >= 7.2 client/server.Bruce Momjian2001-08-15
| | | | | | | Allow pg_shadow to be MD5 encrypted. Add ENCRYPTED/UNENCRYPTED option to CREATE/ALTER user. Add password_encryption postgresql.conf option. Update wire protocol version to 2.1.
* Add convert.Tatsuo Ishii2001-08-15
|
* Add conver/convert2 functions. They are similar to the SQL99's convert.Tatsuo Ishii2001-08-15
|
* Put back changes I overwrote packaging 7.1.3.Bruce Momjian2001-08-14
|
* Put back changes I overwrote in packaging 7.1.3.Bruce Momjian2001-08-14
|
* sum() on int2 and int4 columns now uses an int8, not numeric, accumulatorTom Lane2001-08-14
| | | | | | | | | | | | | | | | | | | | for speed reasons; its result type also changes to int8. avg() on these datatypes now accumulates the running sum in int8 for speed; but we still deliver the final result as numeric, so that fractional accuracy is preserved. count() now counts and returns in int8, not int4. I am a little nervous about this possibly breaking users' code, but there didn't seem to be a strong sentiment for avoiding the problem. If we get complaints during beta, we can change count back to int4 and add a "count8" aggregate. For that matter, users can do it for themselves with a simple CREATE AGGREGATE command; the int4inc function is still present, so no C hacking is needed. Also added max() and min() aggregates for OID that do proper unsigned comparison, instead of piggybacking on int4 aggregates. initdb forced.
* Add HISTORY for 7.1.3. Packaging done.Bruce Momjian2001-08-14
|
* Fix brokenness of nested EXCEPT/INTERSECT queries. prepunion was beingTom Lane2001-08-14
| | | | | | a tad sloppy about generating the targetlist for some nodes, by generating a tlist entry that claimed to be a constant when the value wasn't actually constant. This caused setrefs.c to do the wrong thing later on.
* Make LANCOMPILER clause in CREATE LANGUAGE optional. Allow "identifier"Peter Eisentraut2001-08-13
| | | | | | | | | | | | syntax for language names (instead of 'string'). createlang now handles the case where a second language uses the same call handler as an already installed language (e.g., plperl/plperlu). droplang now handles the reverse case, i.e., dropping a language where the call handler is still used by another language. Moreover, droplang can now be used to drop any user-defined language, not just the supplied ones.
* Make hashjoin give the right answer with toasted input data.Tom Lane2001-08-13
|
* Add comparison operators and btree indexing support for type bytea.Tom Lane2001-08-13
| | | | From Joe Conway.
* Patch NAME section of reference pages.Bruce Momjian2001-08-13
|
* Make ALTER TABLE RENAME on a view rename the view's on-select rule too.Tom Lane2001-08-12
| | | | Needed to keep pg_dump from getting confused.
* Make pg_dump handle the new privileges.Peter Eisentraut2001-08-12
| | | | | | Don't hardcode the maximum accepted server version, use PG_VERSION instead. Install a notice processor so notices are handled like error messages. Word smithing.
* Clean up some warnings and bugs and make things build easier.Peter Eisentraut2001-08-11
|
* CREATE VIEW with optional column name list wasn't quite right for theTom Lane2001-08-11
| | | | case where there are resjunk columns in the query.
* Document column-name-list option of CREATE VIEW ... which has been thereTom Lane2001-08-10
| | | | awhile, but the man page didn't know it.
* Revert removal of relhaspkey support; fix unnecessary use of pg_index.oid.Tom Lane2001-08-10
|
* Mention that COPY cannot be used on a view (per recent suggestion).Tom Lane2001-08-10
| | | | Other small improvements.
* Since PQoidStatus is deprecated, we should probably stop using it inTom Lane2001-08-10
| | | | our own code ...
* updatePeter Eisentraut2001-08-10
|
* Cleanup some minor oversights in optional-OIDs stuff.Tom Lane2001-08-10
|
* Make OIDs optional, per discussions in pghackers. WITH OIDS is still theTom Lane2001-08-10
| | | | | | | | | | | | default, but OIDS are removed from many system catalogs that don't need them. Some interesting side effects: TOAST pointers are 20 bytes not 32 now; pg_description has a three-column key instead of one. Bugs fixed in passing: BINARY cursors work again; pg_class.relhaspkey has some usefulness; pg_dump dumps comments on indexes, rules, and triggers in a valid order. initdb forced.
* Fix collateral damage from error message cleanup.Tom Lane2001-08-10
|
* message refinementsPeter Eisentraut2001-08-10
|
* No longer need TODO.detail/lock.Bruce Momjian2001-08-10
|
* The portion about the PQgetssl() function in the libpq documentationBruce Momjian2001-08-10
| | | | | | | appears to be duplicated (two identical <listitems> right after each other). Here is a quick patch to remove one instance of it. Magnus Hagander
* Attached is a patch to remove some redundant code in the JDBC driver.Bruce Momjian2001-08-10
| | | | | | | | | | | * Merges identical code from org.postgresql.jdbc[1|2].Statement into org.postgresql.Statement. * Moves escapeSQL() method from Connection to Statement (the only place it's used) * Minor cleanup of the new isolation level stuff. * Minor cleanup of version string handling. Anders Bengtsson
* 1. null-safe interface to GiSTBruce Momjian2001-08-10
| | | | | | | | | | | | | | (as proposed in http://fts.postgresql.org/db/mw/msg.html?mid=1028327) 2. support for 'pass-by-value' arguments - to test this we used special opclass for int4 with values in range [0-2^15] More testing will be done after resolving problem with index_formtuple and implementation of B-tree using GiST 3. small patch to contrib modules (seg,cube,rtree_gist,intarray) - mark functions as 'isstrict' where needed. Oleg Bartunov
* Patch to LOCK multiple tables in one LOCK command.Bruce Momjian2001-08-10
| | | | Neil Padgett
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 16:19:50 +0000