[
https://issues.apache.org/jira/browse/METAMODEL-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182731#comment-15182731
]
ASF GitHub Bot commented on METAMODEL-236:
------------------------------------------
GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/89
METAMODEL-236: Fixed
Fixes the serializability of OperatorType (and FunctionType which I also
found had the same issue)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kaspersorensen/metamodel METAMODEL-236
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/89.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #89
----
commit aeddd80c384d409469b804af7725c6524f933ed9
Author: Kasper Sørensen <[email protected]>
Date: 2016-03-07T08:10:47Z
METAMODEL-236: Fixed
----
> Make OperatorType serializable
> ------------------------------
>
> Key: METAMODEL-236
> URL: https://issues.apache.org/jira/browse/METAMODEL-236
> Project: Apache MetaModel
> Issue Type: Improvement
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
>
> In MetaModel queries are serializable, but it seems that we have missed one
> of the dependent classes/interfaces: OperatorType. This interface does not
> extend Serializable, which means that serialization of queries may go wrong
> if they have e.g. a WhereItem with an operator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
