* User who can create databases can modify pg_database table
Not anymore.
* Interlock to prevent DROP DATABASE on a database with running backends
I think Tom wanted this listed as an achievement, because it's already
done.
* Better interface for adding to pg_group
Done.
* Allow array on int8[]
Done. (Credit to Thomas, thought, he just forgot to apply the patch.)
* Make Absolutetime/Relativetime int4 because time_t can be int8 on some
ports
Does this mean the abstime/reltime types or all of them? I thought the
former were deprecated anyway.
* Permissions on indexes, prevent them?
Done (prevented)
* Make postgres user have a password by default
Done. (--pwprompt option, enter it blind twice, echo ALTER USER |
postgres; probably as secure as it gets)
* Update table SET table.value = 3 fails(SQL standard says this is OK)
Not the standard I'm looking at. Someone please enlighten me.
<update statement: searched> ::= UPDATE <table name> SET <set clause list> [
WHERE<search condition> ]
<set clause list> ::= <set clause> [ { <comma> <set clause> }... ]
<set clause> ::= <object column> <equals operator> <update source>
<object column> ::= <column name>
<column name> ::= <identifier>
<identifier> ::= [ <introducer><character set specification> ] <actual identifier>
<introducer>::= <underscore>
<character set specification> ::= { nothing of interest }
<actual identifier> ::= <regular identifier> | <delimited identifier>
{ meaning a non-quoted identifier or a quoted one }
--
Peter Eisentraut Sernanders väg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden