Custom Query (1173 matches)
Results (178 - 180 of 1173)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#549 | fixed | Allow users to revoke an OAuth access grant | ||
Description |
Users can currently authorize an application and view the applications they've authorized, but can not revoke access. We should add support for this. |
|||
#550 | fixed | Fix missing constraint in recent migrations | ||
Description |
A recent migration added a table for the CollectionItem model but didn't add the constraint of: __table_args__ = ( UniqueConstraint('collection', 'media_entry'), {}) Since then we've moved to a new style of "creating models in migrations" which involves actually putting a copy of the original model inside the migrations file to make it easier to create the right database. However, anyone running from git master will currently pick up the "mistaken" commit. There basically seem to be one of two possible solutions:
|
|||
#552 | fixed | GMGTableBase uses default kwarg of {} in methods | ||
Description |
A few places in GMGTableBase have method definitions that look something like: def find_one(cls, query_dict={}): ... This is almost certainly not what the authors intended. The default argument list is only evaluated once during execution, at import time. The code above creates a single dictionary as the default, and if this is mutated down the line, the mutated value becomes the default for subsequent calls. In these particular cases it's unlikely to cause problems -- that argument will almost certainly be passed in -- but in the event it's not, this can cause very strange, difficult to diagnose behavior. The correct approach is to use an immutable value as an argument default. Note that this same problem exists for class level attributes: defining a class such as: class Foo(object): bar = {}
means that for *every* instance of |