Sure
On Thu, Sep 9, 2010 at 6:11 AM, mdipierro wrote:
> No, it does not. It must be done in two queries. Can you send me the
> patch by email? thanks.
>
> On Sep 8, 8:44 pm, Alexey Nezhdanov wrote:
> > Updated version of the patch then. Includes case where there is no such
> row
> > ('create' a
No, it does not. It must be done in two queries. Can you send me the
patch by email? thanks.
On Sep 8, 8:44 pm, Alexey Nezhdanov wrote:
> Updated version of the patch then. Includes case where there is no such row
> ('create' action).
> However, I'm not sure if these changes are GAE-compartible.
Updated version of the patch then. Includes case where there is no such row
('create' action).
However, I'm not sure if these changes are GAE-compartible. Not sure if
bigtable likes .belongs on multiple columns.
Can anybody test?
Regards
Alexey.
--- tools.py_ 2010-09-08 08:40:22.266751051 +0400
I think this should be considered a bug and I agree with the change.
Anybody opposed?
Massimo
On Sep 7, 11:46 pm, Alexey Nezhdanov wrote:
> Hi. I think that I found some inconsistency in the topic.
> When you do, say,
> auth.add_permission(group_id) - it assumes the permission name 'any', table
4 matches
Mail list logo
