Tom, et al,
Looks like Andrew's GSoC student has gotten busy at his new job, so I'm
back on to this and hope to have a new patch ready to go for the Sept.
commitfest. If anyone's interested in helping out, feel free to drop me
a line.
* Tom Lane ([EMAIL PROTECTED]) wrote:
> It occurs to me that
* Andrew Dunstan ([EMAIL PROTECTED]) wrote:
> Tom Lane wrote:
>> I'm not sure where we go from here. Your GSOC student has disappeared,
>> right? Is anyone else willing to take up the patch and work on it?
>
> No, he has not disappeared at all. He is going to work on fixing issues
> and getting
Tom Lane wrote:
I'm not sure where we go from here. Your GSOC student has disappeared,
right? Is anyone else willing to take up the patch and work on it?
No, he has not disappeared at all. He is going to work on fixing issues
and getting the work up to SQL99 l
Stephen Frost <[EMAIL PROTECTED]> writes:
> * Tom Lane ([EMAIL PROTECTED]) wrote:
>> What I think would be a more desirable solution is that the table ACL
>> still sets the table-level INSERT or UPDATE privilege bit as long as
>> you have any such privilege. ...
> I agree with this approach and fe
Greetings,
This really probably should have gone to -hackers rather than just back
to -patches, so here it is. Comments welcome.
* Tom Lane ([EMAIL PROTECTED]) wrote:
> I'm not sure where we go from here. Your GSOC student has disappeared,
> right? Is anyone else willing to take up the patch a
