Support types that does not have an equality operator #61
Labels
Comments
yugo-n
added
documentation
This was referenced Jun 6, 2023
yugo-n
added a commit
that referenced
this issue
Aug 31, 2023
Currently, types that does not have an equality operator cannot be used in the target list of the view definition, because all of target list entries are used for comparison to identify rows to be updated or deleted in the view. Previously, an error is raised at the time such view is incrementally maintained, this is fixed to check that at the view creation time. This restriction may be relaxed in future after we can use an index to identify rows in the view. Issue #61
yugo-n
added a commit
that referenced
this issue
Aug 31, 2023
Currently, types that does not have an equality operator cannot be used in the target list of the view definition, because all of target list entries are used for comparison to identify rows to be updated or deleted in the view. Previously, an error is raised at the time such view is incrementally maintained, this is fixed to check that at the view creation time. This restriction may be relaxed in future after we can use an index to identify rows in the view. Issue #61
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an IMMV contains a column whose type does not have an equality operator, for example, json or xml, the following error is raised.
The current pg_ivm doesn't support such types. So, this should be documented and also checked in create_immv.
Moreover, I would like to allow to use such type in future.
The text was updated successfully, but these errors were encountered: