> "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > No, I mean that we don't drop the user. You go:
> > ALTER USER chriskl COPY PERMISSIONS FROM blah;
>
> That seems cleaner to me than the DROP thingy.
>
> You could only easily implement this in the current database --- but
> since it's not a DROP, one could repeat it in each database as needed.
Could someone perhaps add it to TODO then (so I don't forget about it)? I
can't promise that I can implement it...
Chris