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
but it always return me error like this: "error": "pg: can't find column=code in model=BankAccount (prefix the column with underscore or use discard_unknown_columns)"
Expected Behavior
The return under the Relation must be the bank table with prefix on column bank.image
So I expect to get output like this:
The return in Relation function always referring to bank_account not bank and give me this error: "error": "pg: can't find column=code in model=BankAccount (prefix the column with underscore or use discard_unknown_columns)"
Context (Environment)
I'm using v10
The text was updated successfully, but these errors were encountered:
irmarini
changed the title
Can't add column expression in Relation function
ColumnExpr does'nt work in Relation function
Mar 23, 2021
irmarini
changed the title
ColumnExpr does'nt work in Relation function
ColumnExpr doesn't work in Relation function
Mar 23, 2021
Issue tracker is used for reporting bugs and discussing new features. Please use
Discord or stackoverflow for supporting
issues.
Hi, I'm using go-pg to add prefix to a value of a column in a relation but I always get error column not found. My model:
I want to add prefix into column image in table bank like this:
but it always return me error like this:
"error": "pg: can't find column=code in model=BankAccount (prefix the column with underscore or use discard_unknown_columns)"
Expected Behavior
The return under the Relation must be the bank table with prefix on column bank.image
So I expect to get output like this:
Current Behavior
The return in Relation function always referring to bank_account not bank and give me this error:
"error": "pg: can't find column=code in model=BankAccount (prefix the column with underscore or use discard_unknown_columns)"
Context (Environment)
I'm using v10
The text was updated successfully, but these errors were encountered: