You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If create_pk is True, an autogenerated PK (defaults to id) is created. However this is not exposed on the return model from a query, so methods like update() or delete() that require a primary key cant be called in this case (if the Model has a custom named PK then that works).
After a lot of thought, this will be fixed by making the auto-generated pk compulsory and removing the option to rename it. The ability to rename or remove the auto-increment field may be added again in future releases once the code is cleaned up a bit.
Work on this is in #39 which will close this when complete
The text was updated successfully, but these errors were encountered:
If
create_pk
is True, an autogenerated PK (defaults toid
) is created. However this is not exposed on the return model from a query, so methods likeupdate()
ordelete()
that require a primary key cant be called in this case (if the Model has a custom named PK then that works).After a lot of thought, this will be fixed by making the auto-generated pk compulsory and removing the option to rename it. The ability to rename or remove the auto-increment field may be added again in future releases once the code is cleaned up a bit.
Work on this is in #39 which will close this when complete
The text was updated successfully, but these errors were encountered: