tickets_full: 3389

This data as json

id created changetime last_pulled_from_trac stage status component type severity version resolution summary description owner reporter keywords easy has_patch needs_better_patch needs_tests needs_docs ui_ux
3389 2007-01-29 12:31:11 2007-01-29 16:09:47 2019-06-24 00:51:20.551408 Design decision needed closed Database layer (models, ORM)     master fixed Allow m2m sets to be assigned by primary key value At present, m2m relations must be specified using a list of object instances: {{{ john = Author(...) john.save() fred = Author(...) fred.save() Article.authors = [john, fred] }}} This proposal (and patch) would allow m2m relations be specified using primary key values in place of the object instance: {{{ Article.authors = [john.id, fred.id] # or, if you know the pk values to begin with... Article.authors = [4,7] }}} The reason for this is twofold: 1. For parity with the ability to set m2o related objects by primary key (using Article.author_id = 3) 2. To simplify deserialization, removing the need for a query to find related objects while deserializing m2m sets. adrian russellm m2m primary key 0 1 0 0 1 0
Powered by Datasette · Query took 6.495ms