We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated Columns
Postgres has a handy feature called generated columns. These are columns that can only be read but not be written.
Unfortunately they don't seem to work with Jennifer at the moment (omitting them from the mapping doesn't work, neither does marking them as virtual).
virtual
Maybe it's possible with a custom converter? (is there a way for a converter to completely strip the column from updates and inserts?)
Otherwise it would be nice to have support for readonly-columns at some point. (not urgent for my use-case - just a "nice to have" feature request)
The text was updated successfully, but these errors were encountered:
Unfortunately, currently Jennifer doesn't support generated columns. Added to the roadmap
Sorry, something went wrong.
FYI master branch received this functionality. It'll take some time to prepare new release
No branches or pull requests
Postgres has a handy feature called generated columns. These are columns that can only be read but not be written.
Unfortunately they don't seem to work with Jennifer at the moment
(omitting them from the mapping doesn't work, neither does marking them as
virtual
).Maybe it's possible with a custom converter?
(is there a way for a converter to completely strip the column from updates and inserts?)
Otherwise it would be nice to have support for readonly-columns at some point.
(not urgent for my use-case - just a "nice to have" feature request)
The text was updated successfully, but these errors were encountered: