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
A common use case (I'm guessing, since that's what I'm doing) is to:
Define models => do operations in dfs => save back down as models
This is kind of fiddly because of the column translations when dealing with fk columns.
read_frame(verbose = False) returns an _id suffix for the pk, and not for the fks
but Model(**kwargs) requires an _id suffix for the pk and also for the fks
So there's this translation that's happening that I either circumvent or do some fiddling to undo, the origin is the line:
fieldnames= [f.nameforfinfields]
I'm wondering whether a default of:
fieldnames= [f.attnameforfinfields]
might make more sense, although it's easy enough to wrap this and pass those fieldnames in. I'm curious whether there's a deeper reason for the current default.
The text was updated successfully, but these errors were encountered:
A common use case (I'm guessing, since that's what I'm doing) is to:
Define models => do operations in dfs => save back down as models
This is kind of fiddly because of the column translations when dealing with fk columns.
read_frame(verbose = False) returns an _id suffix for the pk, and not for the fks
but Model(**kwargs) requires an _id suffix for the pk and also for the fks
So there's this translation that's happening that I either circumvent or do some fiddling to undo, the origin is the line:
I'm wondering whether a default of:
might make more sense, although it's easy enough to wrap this and pass those fieldnames in. I'm curious whether there's a deeper reason for the current default.
The text was updated successfully, but these errors were encountered: