- 07 10月, 1999 3 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
First step in cleaning up backend initialization code. Fix for FATAL: now FATAL is ERROR + exit.
-
由 Bruce Momjian 提交于
-
- 06 10月, 1999 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Hiroshi Inoue 提交于
This may solve a TODO item * Recover or force failure when disk space is exhausted
-
由 Vadim B. Mikheev 提交于
heap_insert() any more. No reasons to do it, and old comments said about this.
-
由 Bruce Momjian 提交于
insert, update or delete. It will return -1 on error, although I've yet to an error situation to prove that out! Vince
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 05 10月, 1999 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 04 10月, 1999 12 次提交
-
-
由 Thomas G. Lockhart 提交于
A few other changes, but I forget what :(
-
由 Bruce Momjian 提交于
2 line GetIsNull diffs, we now need this too: Patrick Welche
-
由 Thomas G. Lockhart 提交于
Still need the code updated for LO examples.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
display of default expressions isn't quite so ugly.
-
由 Tom Lane 提交于
quite the same way that transformInsertStatement does, so that an expression could be accepted by CREATE TABLE and then fail when used. Also, put back check that CONSTRAINT expressions must yield boolean...
-
由 Tom Lane 提交于
expressions in CREATE TABLE. There is no longer an emasculated expression syntax for these things; it's full a_expr for constraints, and b_expr for defaults (unfortunately the fact that NOT NULL is a part of the column constraint syntax causes a shift/reduce conflict if you try a_expr. Oh well --- at least parenthesized boolean expressions work now). Also, stored expression for a column default is not pre-coerced to the column type; we rely on transformInsertStatement to do that when the default is actually used. This means "f1 datetime default 'now'" behaves the way people usually expect it to. BTW, all the support code is now there to implement ALTER TABLE ADD CONSTRAINT and ALTER TABLE ADD COLUMN with a default value. I didn't actually teach ALTER TABLE to call it, but it wouldn't be much work.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
--enable-debug adds -g (unconditionally) --disable-debug removes -g (if it was already in there somehow) (giving neither does nothing) Since none of the templates default CFLAGS with a -g you're not likely to end up with two -g flags. Not that they'd hurt though. It doesn't do anything about C++. Peter Eisentraut
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 03 10月, 1999 4 次提交
-
-
由 Tom Lane 提交于
make it call eval_const_expressions() so that it doesn't have to know).
-
由 Tom Lane 提交于
not just C, so that ISCACHABLE attribute can be specified for user-defined functions. Get rid of ParamString node type, which wasn't actually being generated by gram.y anymore, even though define.c thought that was what it was getting. Clean up minor bug in dfmgr.c (premature heap_close).
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
works if finite() is a function. Patch from Christof Petig.
-
- 02 10月, 1999 3 次提交
-
-
由 Tom Lane 提交于
modifyAggrefQual. This routine really, really needs to be retired, but until we have subselects in FROM there's no chance of doing the job right. In the meantime try to respond to unhandlable cases with elog rather than coredump.
-
由 Tom Lane 提交于
in the Expr nodes they produce. This fixes a few cases of errors like 'typeidTypeRelid: Invalid type - oid = 0' caused by calling parser-related routines on expression trees that have already been processed by planner- related routines.
-
由 Tom Lane 提交于
they have no hardwired limit on the length of a rule's text. Fix a couple of minor bugs in passing --- deparsed UPDATE queries didn't have quotes around relation name, and quotes and backslashes in constant values weren't backslash-quoted.
-
- 01 10月, 1999 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Thomas G. Lockhart 提交于
Seems to read better this way...
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
committed, but will be within a week or two). Actually include the reference page into the docs...
-
由 Thomas G. Lockhart 提交于
-
由 Thomas G. Lockhart 提交于
the Programmer's Guide.
-
由 Tom Lane 提交于
expression_tree_mutator rather than ad-hoc tree walking code. This shortens the code materially and fixes a fair number of sins of omission. Also, change modifyAggrefQual to *not* recurse into subselects, since its mission is satisfied if it removes aggregate functions from the top level of a WHERE clause. This cures problems with queries of the form SELECT ... WHERE x IN (SELECT ... HAVING something-using-an-aggregate), which would formerly get mucked up by modifyAggrefQual. The routine is still fundamentally broken, of course, but I don't think there's any way to get rid of it before we implement subselects in FROM ...
-
- 30 9月, 1999 1 次提交
-
-
由 Jan Wieck 提交于
RI_FKey_... constrint triggers when looking for illegal pg_proc entries. Jan
-