- 22 11月, 2005 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 21 11月, 2005 1 次提交
-
-
由 Alvaro Herrera 提交于
process of dropping roles by dropping objects owned by them and privileges granted to them, or giving the owned objects to someone else, through the use of the data stored in the new pg_shdepend catalog. Some refactoring of the GRANT/REVOKE code was needed, as well as ALTER OWNER code. Further cleanup of code duplication in the GRANT code seems necessary. Implemented by me after an idea from Tom Lane, who also provided various kind of implementation advice. Regression tests pass. Some tests for the new functionality are also added, as well as rudimentary documentation.
-
- 20 11月, 2005 2 次提交
-
-
由 Tom Lane 提交于
not only the array contents, before claiming two arrays are equal. Per recent discussion.
-
由 Andrew Dunstan 提交于
DROP objecttype IF EXISTS for the following objects: table view index sequence schema type domain conversion
-
- 19 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
the array (for array_push) or higher-dimensional array (for array_cat) rather than decrementing it as before. This avoids generating lower bounds other than one for any array operation within the SQL spec. Per recent discussion. Interestingly, this seems to have been the original behavior, because while updating the docs I noticed that a large fraction of relevant examples were *wrong* for the old behavior and are now right. Is it worth correcting this in the back-branch docs?
-
- 18 11月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
J.Kuwamura
-
由 Tom Lane 提交于
functionality, but I still need to make another pass looking at places that incidentally use arrays (such as ACL manipulation) to make sure they are null-safe. Contrib needs work too. I have not changed the behaviors that are still under discussion about array comparison and what to do with lower bounds.
-
- 17 11月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
< so duplicate checking can be easily performed. > so duplicate checking can be easily performed. It is possible to > do it without a unique index if we require the user to LOCK the table > before the MERGE.
-
由 Bruce Momjian 提交于
< * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
-
- 16 11月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > To implement this cleanly requires that the table have a unique index > so duplicate checking can be easily performed. >
-
由 Bruce Momjian 提交于
features.
-
- 08 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 05 11月, 2005 6 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
- 04 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
necessary, and be careful to refer to the right version where it is useful to do so. This partially reverts an ill-considered search and replace from a few months ago.
-
- 03 11月, 2005 1 次提交
-
-
由 Neil Conway 提交于
elsewhere.
-
- 02 11月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
From Simon Riggs; cleanup and editorialization by Neil Conway.
-
由 Tom Lane 提交于
-
- 01 11月, 2005 2 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
referential integrity relationships.
-
- 31 10月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 30 10月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
Andreas Seltenreich
-
- 29 10月, 2005 2 次提交
- 28 10月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 27 10月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
< o Allow ALTER TABLE RENAME CONSTRAINT > o Add ALTER TABLE RENAME CONSTRAINT, update index name also
-
由 Bruce Momjian 提交于
> o Have ALTER INDEX update the name of a constraint using that index > o Allow ALTER TABLE RENAME CONSTRAINT
-