- 11 12月, 2000 9 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
all forms of foreign keys be exposed to SQLForeignKeys. This patch is in addition to the ones I mailed yesterday (forget had I changed that as well....) Michael Fork - CCNA - MCP - A+ Network Support - Toledo Internet Access - Toledo Ohio
-
由 Bruce Momjian 提交于
return foreign key information based on the pg_trigger system table. I have tested the patch with (what I believe) is all possible primary/foreign key combinations -- however I may have missed some, so if anyone feels like taking the patch for a test drive, here are some useful links: Michael Fork
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
line 1324: "left-hand" should be "right-hand" BTW: new document looks very good! And the new configure/build process seems much better then before! Thanks! Laser
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
- 10 12月, 2000 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
is the only diff not accounted for by fmgr rewrite...
-
由 Tom Lane 提交于
-
- 09 12月, 2000 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
Thanks Chih-Chang Hsieh <cch@cc.kmu.edu.tw> for finding the bug.
-
由 Tom Lane 提交于
varlena type. (I did not force initdb, but you won't see the fix unless you do one.) Also, make sure all index support operators and functions are careful not to leak memory for toasted inputs; I had missed some hash and rtree support ops on this point before.
-
由 Tom Lane 提交于
mostly just on the WAL logfile nowadays. But if people want to disable fsync for performance, why should we say no?
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
value greater than one. The behavior this sought to disallow doesn't seem any less confusing than the other behaviors of cached sequences. Improve wording of some error messages, too. Update documentation accordingly. Also add an explanation that aborted transactions do not roll back their nextval() calls; this seems to be a FAQ, so it ought to be mentioned here...
-
- 08 12月, 2000 10 次提交
-
-
由 Hiroshi Inoue 提交于
-
由 Hiroshi Inoue 提交于
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
or return type.
-
由 Tom Lane 提交于
length is less than original string length.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
As I read it, the spec requires a non-null result in some cases where one of the inputs is NULL: specifically, if the other endpoint of that interval is between the endpoints of the other interval, then the result is known TRUE despite the missing endpoint. The spec could've been a lot simpler if they did not intend this behavior. I did not force an initdb for this change, but if you don't do one you'll still see the old strict-function behavior.
-
- 07 12月, 2000 7 次提交
-
-
由 Hiroshi Inoue 提交于
if the transaction has already been committed ?
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
transformForUpdate does: it should recurse into subqueries.
-
由 Tom Lane 提交于
It could be recursing into a sub-query where there was already a FOR UPDATE clause.
-
由 Tom Lane 提交于
work where we can (given that the executor only handles it at top level) and generate an error where we can't. Note that while the parser has been allowing views to say SELECT FOR UPDATE for a few weeks now, that hasn't actually worked until just now.
-
由 Marc G. Fournier 提交于
update VERSION to 7.1beta1..
-