summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Update TODO list.Bruce Momjian2001-05-301-5/+6
|
* Remove unused, redundant header files.Tom Lane2001-05-302-42/+0
|
* Fix broken $Header$ declaration.Tom Lane2001-05-301-1/+1
|
* Properly compute max sys oid for 7.0 and 7.1.Bruce Momjian2001-05-301-4/+10
|
* I just got bitten by this too. I use type timestamp in theBruce Momjian2001-05-301-4/+14
| | | | | | | | | | | | | | | | | | | | | | database, and often need the latest timestamp, but want to format it as a date. With 7.0.x, I just select ts from foo order by ts desc limit 1 and in java: d = res.getDate(1); but this fails everywhere in my code now :( http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html says The ResultSet.getXXX methods will attempt to convert whatever SQL type was returned by the database to whatever Java type is returned by the getXXX method. Palle Girgensohn
* Fix missing relation in FROM causing NOTICE. Cleanup.Bruce Momjian2001-05-301-7/+2
|
* Remove reference to pg_class.relhaspkey from code. Column is unused.Bruce Momjian2001-05-301-14/+2
|
* Mark as unused:Bruce Momjian2001-05-301-5/+5
| | | | | | | | > Are these columns in pg_class: > relukeys | relfkeys | relhaspkey > unused or what? Christopher Kings
* Update TODO list.Bruce Momjian2001-05-301-3/+5
|
* Remove SEP_CHAR from /contrib.Bruce Momjian2001-05-301-8/+7
|
* Remove SEP_CHAR, replace with / or '/' as appropriate.Bruce Momjian2001-05-3010-62/+55
|
* Fix for Druid. We did not support some PROCEDURE queries.Bruce Momjian2001-05-302-2/+2
| | | | Dave Cramer
* This is a docs patch to go with my DROP CONSTRAINT patch.Bruce Momjian2001-05-301-30/+33
| | | | Christopher Kings
* These patches should fix check constraints not inheritingBruce Momjian2001-05-303-1/+180
| | | | | | | | when added by alter table add constraint. The first file patches backend/commands/command.c and the latter is a patch to the alter table regression test. Stephan Szabo
* Playing with the earthdistance stuff, and found I needed the followingBruce Momjian2001-05-301-2/+2
| | | | | | patch: Larry Rosenman
* Attached is my patch that adds DROP CONSTRAINT support to PostgreSQL. IBruce Momjian2001-05-303-6/+215
| | | | | | | | | | | | | | | | | | | | basically want your guys feedback. I have sprinkled some of my q's thru the text delimited with the @@ symbol. It seems to work perfectly. [ Removed @@ comments because patch was reviewed. ] At the moment it does CHECK constraints only, with inheritance. However, due to the problem mentioned before with the mismatching between inherited constraints it may be wise to disable the inheritance feature for a while. it is written in an extensible fashion to support future dropping of other types of constraint, and is well documented. Please send me your comments, check my use of locking, updating of indices, use of ERROR and NOTICE, etc. and I will rework the patch based on feedback until everyone is happy with it... Christopher Kings
* Correct obsolete example of FROM-less query.Tom Lane2001-05-301-2/+2
|
* In chapter:Bruce Momjian2001-05-301-2/+2
| | | | | | | | | | | | | | | | | | | 7.7. Keys you have However, my application requires that each collection will also have a unique name. Why? So that a human being who wants to modify a collection will be able to identify it. It's much harder to know, if you have two collections named "Life Science", the the one tagged 24433 is the one you need, and the one tagged 29882 is not I think 'the the' shouldn't be repeated twice. Although taken from an email it would be cool to fix. Cheers, Maxim Maletsky
* Further conversions to Version 1 API. Also, fix boolean return to useD'Arcy J.M. Cain2001-05-301-7/+7
| | | | PG_RETURN_BOOL(0) instead of return 0.
* Add missing comma.D'Arcy J.M. Cain2001-05-301-1/+1
|
* Make text <=> char conversion functions convert zero character to andTom Lane2001-05-281-5/+33
| | | | | | from an empty text string. This makes them consistent with the de facto behavior of type char's I/O conversion functions, and avoids generating text values with embedded nulls, which confuse many text operators.
* Cause plpgsql's PERFORM to behave according to its documentation,Tom Lane2001-05-282-19/+41
| | | | | | | | | | | | which says that PERFORM will execute any SELECT query and discard the result. The former implementation would in fact raise an error if the result contained more than one row or more than one column. Also, change plpgsql's error-logging mechanism to emit the additional messages about error location at NOTICE rather than DEBUG level. This allows them to be seen by the client without having to dig into the postmaster log file (which may be nonexistent or inaccessible by the client).
* Upgraded code to use the current version 1 calling conventions.D'Arcy J.M. Cain2001-05-281-32/+47
|
* Suppress useless memmove() when buffer already contains left-justifiedTom Lane2001-05-281-6/+12
| | | | data.
* markup fixPeter Eisentraut2001-05-281-2/+1
|
* Update TODO list.Bruce Momjian2001-05-281-2/+2
|
* Sample output that appears below the table attributes for \d:Bruce Momjian2001-05-281-2/+3
| | | | | | | | | | | | | | | Indicies: palm_buy_date_idx palm_user_date_idx Primary Key: palm_buyers_pkey Unique Key: palm_buyers_username Constraint: "$1" ((sex = 'M'::bpchar) OR (sex = 'F'::bpchar)) Note that check constraint name now shown as well. (Makes it a lot easier to test inheritance support in ADD/DROP constraint :) ) Attached is a docs change for psql. Christopher Kings
* This just breaks down the indices in to three groups:Bruce Momjian2001-05-281-15/+79
| | | | | | | | | | | | non-unique: stay as they were unique and primary: become listed as primary keys unique and non-primary: become listed as unique keys I also made it so that it shows the names of check constraints ie: Check: "$1" (a > 5) Christopher Kings
* Fix a message error in utf_to_localTatsuo Ishii2001-05-281-2/+2
|
* Attached is a patch to fix the problem Thomas mentions below. The JDBCBruce Momjian2001-05-282-2/+46
| | | | | | | driver now correctly handles timezones that are offset fractional hours from GMT (ie. -06:30). Barry Lind
* Don't use multi-line string literals.Peter Eisentraut2001-05-271-7/+7
|
* When using a junkfilter, the output tuple should NOT be stored back intoTom Lane2001-05-274-24/+51
| | | | | | | | the same tuple slot that the raw tuple came from, because that slot has the wrong tuple descriptor. Store it into its own slot with the correct descriptor, instead. This repairs problems with SPI functions seeing inappropriate tuple descriptors --- for example, plpgsql code failing to cope with SELECT FOR UPDATE.
* Cause ExecCountSlots() accounting to bear some relationship to reality.Tom Lane2001-05-277-15/+15
| | | | Rather surprising we hadn't seen bug reports about this ...
* Changed use of macros for extracting information. According to commentsD'Arcy J.M. Cain2001-05-271-3/+3
| | | | | | in c.h we should be using the visible structure. We should only see de-TOASTed values in this program. The old method refused to compile because the length macro was no longer an lvalue.
* Fix eqjoinsel() to make use of new statistics.Tom Lane2001-05-271-41/+201
|
* Update TODO list.Bruce Momjian2001-05-271-2/+2
|
* Make UPDATE and DELETE privileges distinct. Add REFERENCES and TRIGGERPeter Eisentraut2001-05-2726-826/+724
| | | | | privileges. INSERT and COPY FROM now require INSERT (only). Add privileges regression test.
* Add NUMERICOID return type. Treat it as floating point for now. ThisD'Arcy J.M. Cain2001-05-271-0/+4
| | | | | could be changed if we create a new Python type that matches it better but NUMERIC <==> FLOAT probably works fine for most cases.
* Mention failure of ANT to delete directories on clean.Bruce Momjian2001-05-251-1/+5
|
* See attached for a small patch that enables plpython to build cleanlyBruce Momjian2001-05-254-6/+13
| | | | | | | | | | | | under Cygwin. This patch together with my previous Python patch: http://postgresql.readysetnet.com/mhonarc/pgsql-patches/2001-05/msg00075.htm l enables full Python support (i.e., configure --with-python) for Cygwin PostgreSQL. Jason Tishler
* Oops, only wanted python change in the last commit. Backing out.Bruce Momjian2001-05-259-208/+15
|
* While changing Cygwin Python to build its core as a DLL (like Win32Bruce Momjian2001-05-2510-20/+210
| | | | | | | | | | | | | | | Python) to support shared extension modules, I have learned that Guido prefers the style of the attached patch to solve the above problem. I feel that this solution is particularly appropriate in this case because the following: PglargeType PgType PgQueryType are already being handled in the way that I am proposing for PgSourceType. Jason Tishler
* Back out, per Peter E.Bruce Momjian2001-05-251-7/+4
| | | | | | | > > The attached patch changes src/interfaces/python/GNUmakefile to use the > > value of DESTDIR like the rest (or at least most) of the PostgreSQL > > makefiles. I found this problem when trying to package a pre-built > > Cygwin PostgreSQL distribution, but this problem is platform independent.
* The attached patch changes src/interfaces/python/GNUmakefile to use theBruce Momjian2001-05-251-4/+7
| | | | | | | | | | | | | | | | | | | | value of DESTDIR like the rest (or at least most) of the PostgreSQL makefiles. I found this problem when trying to package a pre-built Cygwin PostgreSQL distribution, but this problem is platform independent. The problem manifests itself when one tries to install into a stagging area (e.g., to build a tarball) instead of a real install. In this case, pg.py and _pgmodule$(SO) still end up being installed in the configured prefix directory ignoring the value of DESTDIR. Unfortunately, this patch does not handle the case where PostgreSQL and Python are configured with different prefixes. Since the Python Makefile is automatically generated and does not use DESTDIR, I believe that this issue will be difficult to correct. If anyone has ideas on how to fix this issue, then I'm quite willing to rework the patch to take the suggestion into account. Jason Tishler
* The following patch corrects a make install problem when buildingBruce Momjian2001-05-253-4/+8
| | | | | | | | | | | | under Cygwin. The root cause of this problem is that (Sun) java is a native Win32 app and hence does not understand Cygwin Posix style paths. The solution is to use Cygwin's cygpath utility to convert the Posix style JDBC installation directory path into a Win32 one before invoking ant. I'm not sure if my patch is the best way to correct this issue but my goal was to confine the Cygwin specific constructs to Jason Tishler
* Get rid of the following size limit.Hiroshi Inoue2001-05-258-116/+422
| | | | | 1) Query size limit(was 65536) for >=7.0 servers. 2) Text size limit(was 8190) for 7.1 servers.
* Another Makefile fix for qnx patch.Bruce Momjian2001-05-251-5/+5
|
* Fix tabs in Makefile.Bruce Momjian2001-05-251-4/+4
|
* Back out qnx plpgsql/Makefile change and move to src/Makefile.Bruce Momjian2001-05-243-12/+10
|
* I haven't tried building postgres with the Watcom compiler for 7.1 becauseBruce Momjian2001-05-2410-73/+191
| | | | | | | | | | | | | | | | it does not support 64bit integers. AFAIK that's the default data type for OIDs, so I am not surprised that this does not work. Use gcc instead. BTW., 7.1 does not compile as is with gcc either, I believed the required patches made it into the 7.1.1 release but obviously I missed the deadline. Since the ports mailing list does not seem to be archived I have attached a copy of the patch (for 7.1 and 7.1.1). I've just performed a build of a Watcom compiled version and found a couple of bugs in the watcom specific part of that patch. Please use the attached version instead. Tegge, Bernd
View Lorry Controller Status