aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* The attached file: SerializePatch2.tgz, contains a patch forBruce Momjian2001-08-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | org.postgresql.util.Serialize and org.postgresql.jdbc2.PreparedStatement that fixes the ability to "serialize" a simple java class into a postgres table. The current cvs seems completely broken in this support, so the patch puts it into working condition, granted that there are many limitations with serializing java classes into Postgres. The code to do serialize appears to have been in the driver since Postgres 6.4, according to some comments in the source. My code is not adding any totally new ability to the driver, rather just fixing what is there so that it actually is usable. I do not think that it should affect any existing functions of the driver that people regularly depend on. The code is activated if you use jdbc2.PreparedStatement and try to setObject some java class type that is unrecognized, like not String or not some other primitive type. This will cause a sequence of function calls that results in an instance of Serialize being instantiated for the class type passed. The Serialize constructor will query pg_class to see if it can find an existing table that matches the name of the java class. If found, it will continue and try to use the table to store the object, otherwise an SQL exception is thrown and no harm is done. Serialize.create() has to be used to setup the table for a java class before anything can really happen with this code other than an SQLException (unless by some freak chance a table exists that it thinks it can use). I saw a difference in Serialize.java between 7.1.3 and 7.2devel that I didn't notice before, so I had to redo my changes from the 7.2devel version (why I had to resend this patch now). I was missing the fixString stuff, which is nice and is imporant to ensure the inserts will not fail due to embedded single quote or unescaped backslashes. I changed that fixString function in Serialize just a little since there is no need to muddle with escaping newlines: only escaping single quote and literal backslashes is needed. Postgres appears to insert newlines within strings without trouble.
* Fix portability problem in new CLOG code, per report from Rene Pijlman.Tom Lane2001-08-25
|
* Re-apply Array.java patch to new Array.java file to fix compile.Bruce Momjian2001-08-25
|
* Replace implementation of pg_log as a relation accessed through theTom Lane2001-08-25
| | | | | | | | | | | buffer manager with 'pg_clog', a specialized access method modeled on pg_xlog. This simplifies startup (don't need to play games to open pg_log; among other things, OverrideTransactionSystem goes away), should improve performance a little, and opens the door to recycling commit log space by removing no-longer-needed segments of the commit log. Actual recycling is not there yet, but I felt I should commit this part separately since it'd still be useful if we chose not to do transaction ID wraparound.
* Add ENCRYPTED/UNENCRYPTED control in createuser script.Bruce Momjian2001-08-25
|
* Add MD5 to win32.makBruce Momjian2001-08-25
|
* Add intended Array.java file that accidentally was patched into theBruce Momjian2001-08-25
| | | | wrong directory.
* update from Serguei MokhovPeter Eisentraut2001-08-25
|
* Hide backend debug output in initdb by default. To that end, the bootstrapPeter Eisentraut2001-08-25
| | | | backend gets on -o option like the regular backend.
* c.h needs to include postgres_ext.h to be self-contained.Peter Eisentraut2001-08-24
|
* Missed this part in pg_config.h rename.Peter Eisentraut2001-08-24
|
* Add ecpg --help and --version. Renumber the exit status codes, which werePeter Eisentraut2001-08-24
| | | | documented wrong.
* Start adding some more documentation about the number types. MakePeter Eisentraut2001-08-24
| | | | bigserial and alias for serial8 for consistency with bigint/int8.
* Reverse sense of comparison in psql socket test, per Tom Lane.Bruce Momjian2001-08-24
|
* There are two problems when compiling libpq.dll and psql.exeBruce Momjian2001-08-24
| | | | | | | on Windows. I'm not sure it is the best way to fix them (see patch below.) Mikhail Terekhov with mods by Tom Lane
* Attached is a patch to fix the current issues with building under jdbc1.Bruce Momjian2001-08-24
| | | | | | | | | | | This patch moves the logic that looks up TypeOid, PGTypeName, and SQLTypeName from Field to Connection. It is moved to connection since it needs to differ from the jdbc1 to jdbc2 versions and Connection already has different subclasses for the two driver versions. It also made sense to move the logic to Connection as some of the logic was already there anyway. Barry Lind
* Rename config.h to pg_config.h and os.h to pg_config_os.h, fix a number ofPeter Eisentraut2001-08-24
| | | | places that were including the wrong files.
* Ensure that all TransactionId comparisons are encapsulated in macrosTom Lane2001-08-23
| | | | | (TransactionIdPrecedes, TransactionIdFollows, etc). First step on the way to transaction ID wrap solution ...
* Allow the return value of an SQL function to be binary-compatible withTom Lane2001-08-23
| | | | | the declared result type, rather than requiring exact type match as before. Per pghackers discusssion of 14-Aug.
* Add option to output SET SESSION AUTHORIZATION commands rather thanPeter Eisentraut2001-08-22
| | | | | \connect, to avoid possible password prompts and such, at the drawback of having to have superuser access.
* remove no longer needed -Wno-errorPeter Eisentraut2001-08-22
|
* Update GiST for new pg_opclass arrangement (finally a clean solutionTom Lane2001-08-22
| | | | | | for haskeytype). Update GiST contrib modules too. Add linear-time split algorithm for R-tree GiST opclass. From Oleg Bartunov and Teodor Sigaev.
* Attached is a simple one line patch for the problem reported in theBruce Momjian2001-08-22
| | | | | | | | | | | | | | | following email. > > The problem: When I call getBigDecimal() on a ResultSet, it > > sometimes throws an exception: > > > > Bad BigDecimal 174.50 > > at org.postgresql.jdbc2.ResultSet.getBigDecimal(ResultSet.java:373) > > at org.postgresql.jdbc2.ResultSet.getBigDecimal(ResultSet.java:984) > > ...blah blah blah... > > org.postgresql.util.PSQLException: Bad BigDecimal 174.50 Barry Lind
* Here's a resend of the patch.gz. I gunzip'ed it fine hereBruce Momjian2001-08-21
| | | | | | | | | | | | so it may be a transit problem. Also removed the 'txt' suffix in case that was confusing some transport layer trying to be too inteligent for our own good. This may have been because the Array.java class from the previous patch didn't seem to have made it into the snapshot build for some reason. This patch should at least fix that issue. Greg Zoller
* Remove special-case treatment of all-zeroes MAC address, per today'sTom Lane2001-08-21
| | | | discussion in pgsql-general.
* > Ok, where's a "system dependent hack" :)Bruce Momjian2001-08-21
| | | | | | | | | | | | | | | | | | | | > It seems that win9x doesn't have the "netmsg.dll" so it defaults to "normal" > FormatMessage. > I wonder if one could load wsock32.dll or winsock.dll on those systems > instead of netmsg.dll. > > Mikhail, could you please test this code on your nt4 system? > Could someone else test this code on a win98/95 system? > > It works on win2k over here. It works on win2k here too but not on win98/95 or winNT. Anyway, attached is the patch which uses Magnus's my_sock_strerror function (renamed to winsock_strerror). The only difference is that I put the code to load and unload netmsg.dll in the libpqdll.c (is this OK Magnus?). Mikhail Terekhov
* Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions inTom Lane2001-08-21
| | | | | | | | | | | | | | | | | | | | pgsql-hackers. pg_opclass now has a row for each opclass supported by each index AM, not a row for each opclass name. This allows pg_opclass to show directly whether an AM supports an opclass, and furthermore makes it possible to store additional information about an opclass that might be AM-dependent. pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we previously expected the user to remember to provide in CREATE INDEX commands. Lossiness is no longer an index-level property, but is associated with the use of a particular operator in a particular index opclass. Along the way, IndexSupportInitialize now uses the syscaches to retrieve pg_amop and pg_amproc entries. I find this reduces backend launch time by about ten percent, at the cost of a couple more special cases in catcache.c's IndexScanOK. Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane. initdb forced.
* Move WAL params higher in file, next to fsync option.Bruce Momjian2001-08-21
|
* Add -Wno-error because of "unclean" flex output.Peter Eisentraut2001-08-21
|
* Regroup GEQO configs.Bruce Momjian2001-08-21
|
* Fix SCM_CREDS for FreeBSD, from Teodor Sigaev.Bruce Momjian2001-08-21
|
* Add new jdbc array file.Bruce Momjian2001-08-21
|
* Add ECPGd_cardinality to end of enum list so ecpg compiles.Bruce Momjian2001-08-21
|
* Add missing include for SCM_CREDS.Bruce Momjian2001-08-21
|
* Fix SO_PEERCRED printf bug added with SCM_CREDS cleanup.Bruce Momjian2001-08-21
|
* Fix a lot of compile errors on unix.Hiroshi Inoue2001-08-21
| | | | Fix '\\' handling for bytea type.
* >Bruce Momjian2001-08-21
| | | | | | | | | | | | | | | | | | | | > Shouldn't > > throw new PSQLException("metadata unavailable"); > > in getTypeInfo() be something like: > > throw new PSQLException("postgresql.meta.unavailable"); > > to allow translation of the error message in the > errors*.properties files? You're right. Attached is an updated patch that also includes a message in error.properties. I've attempted a French message in errors_fr.properties but beware that I haven't written French in quite a few years. Don't know Italian, German, or Dutch so I can't do those. Liam Stewart
* Add SCM_CREDS to get owner of unix-domain socket on BSD-like systems.Bruce Momjian2001-08-21
|
* One more round of translations and slight message tweaksPeter Eisentraut2001-08-19
|
* - Synced preproc.y with gram.y.Michael Meskes2001-08-19
| | | | - Include some patches by Christof Petig <christof.petig@wtal.de>.
* 1) Change all internal SQL function calls fromHiroshi Inoue2001-08-18
| | | | | | | | 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).
* Ensure to hold an exclusive lock while reindexing a relation.Hiroshi Inoue2001-08-17
| | | | This is mainly to help developers to understand the code.
* A little more code reorg for MD5/crypt.Bruce Momjian2001-08-17
|
* Reorder MD5/crypt so MD5 comes first in the code.Bruce Momjian2001-08-17
|
* Remove some unneeded dashes from libpq comments.Bruce Momjian2001-08-17
|
* Add \n to libpq print output where needed.Bruce Momjian2001-08-17
|
* This patch updates some comments in the DatabaseMetaData classes toBruce Momjian2001-08-17
| | | | | | | reflect a mail thread that discussed our conformance (or lack thereof) to the SQL92 spec. Barry Lind
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-02 23:32:14 +0000