- 23 8月, 2002 12 次提交
-
-
由 Bruce Momjian 提交于
> * Add GUC parameter to print queries that generate errors
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
docs and find the other obsolete statements that no doubt lurk.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
for a good long while, I see no reason to maintain this original copy.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Marc G. Fournier 提交于
Remove all traces of the ODBC driver, which is now on GBorg as the psqlodbc project ...
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
addition of a column list clause to the COPY command. Spotted by Martin Renters.
-
- 22 8月, 2002 21 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
tighten foreign-key check (a self-reference should not prevent TRUNCATE), improve error message, cause a relation's TOAST table to be truncated along with the relation.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
>>" It's also possible to select no escape character by writing ESCAPE ''. >>In this case there is no way to turn off the special meaning of >>underscore and percent signs in the pattern." Joe Conway
-
由 Bruce Momjian 提交于
for repeat(). Again, somewhat off-the-cuff, so I might have missed something... test=# select lpad('xxxxx',1431655765,'yyyyyyyyyyyyyyyy'); ERROR: Requested length too large test=# select rpad('xxxxx',1431655765,'yyyyyyyyyyyyyyyy'); ERROR: Requested length too large (That's on a Unicode DB, haven't tested other encodings but AFAICT this fix should still work.) Neil Conway
-
由 Bruce Momjian 提交于
> Neil Conway <neilc@samurai.com> writes: > > + /* Check for integer overflow */ > > + if (tlen / slen != count) > > + elog(ERROR, "Requested buffer is too large."); > > What about slen == 0? Good point -- that wouldn't cause incorrect results or a security problem, but it would reject input that we should really accept. Revised patch is attached. Neil Conway
-
由 Bruce Momjian 提交于
> > is a patch to add some cross-referencing. Oliver Elphick
-
由 Bruce Momjian 提交于
constraints The issue with finding and removing foreign key constraints is no longer an issue, so please apply the attached. It does NOT check for rules or on delete triggers (old style foreign keys) as those are difficult to deal with (remove, truncate, re-add). Rod Taylor
-
由 Bruce Momjian 提交于
> * Allow bytea to handle LIKE with non-TEXT patterns
-
由 Bruce Momjian 提交于
bytealike to TEXT. This leaves like_escape_bytea() without anything to do, but I left it in place in anticipation of the eventual bytea pattern selectivity functions. If there is agreement that this would be the best long term solution, I'll take it as a TODO for 7.4. Joe Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
replace(string, from, to) -- replaces all occurrences of "from" in "string" to "to" split(string, fldsep, column) -- splits "string" on "fldsep" and returns "column" number piece to_hex(int32_num) & to_hex(int64_num) -- takes integer number and returns as hex string Joe Conway
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Marc G. Fournier 提交于
Okay, libpq++ is moved to GBorg, and all traces of it have been removed from the core repository ... I haven't *moved* the libpq++ files out of the tree, mainly as we want to keep them in place for past branches ... Peter, I think I've covered all the files I need, and re-ran autoconf to make sure the configure file is in place properly ...
-
由 Tom Lane 提交于
with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
- 21 8月, 2002 5 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
Use off_t and size_t in pg_dump to handle file offset arithmetic correctly.
-
由 Tom Lane 提交于
code is broken, but any small change in the output format might overrun the buffer with the old size.
-
由 Tom Lane 提交于
From Rod Taylor.
-
- 20 8月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
FOUND is set whenever a SELECT INTO returns > 0 rows, *or* when an INSERT, UPDATE, or DELETE affects > 0 rows. We implemented the first part of this behavior, but not the second. I also improved the documentation on the various situations in which FOUND can be set (excluding inside FOR loops, which I still need to think about), and added some regression tests for this behavior. Neil Conway
-
由 Bruce Momjian 提交于
-