Skip to content

[GEOT-4931] Fix comparison of attribute bindings in DataUtilities#2525

Merged
aaime merged 1 commit into
geotools:masterfrom
elahrvivaz:datautilities_compare_bindings
Oct 7, 2019
Merged

[GEOT-4931] Fix comparison of attribute bindings in DataUtilities#2525
aaime merged 1 commit into
geotools:masterfrom
elahrvivaz:datautilities_compare_bindings

Conversation

@elahrvivaz

Copy link
Copy Markdown
Contributor
  • Current DataUtilities isMatch implementation compares the class of the
    attribute descriptor, not the type binding

Signed-off-by: Emilio Lahr-Vivaz elahrvivaz@ccri.com

* Current DataUtilities isMatch implementation compares the class of the
attribute descriptor, not the type binding

Signed-off-by: Emilio Lahr-Vivaz <elahrvivaz@ccri.com>
@aaime

aaime commented Sep 21, 2019

Copy link
Copy Markdown
Member

Makes sense to me, merging.

@nprigour

Copy link
Copy Markdown
Contributor

Hi,
Maybe it is worth to also let DataUtilities provide the so far used functionality by providing two extra methods for DataUtilities.compare() and DataUtilities.isMatch() and differentiate based on an appropriate flag. I suggest this since sometimes it may be useful to have a method allowing the comparison of 2 featureTypes based on their attributes names.

@aaime

aaime commented Oct 7, 2019

Copy link
Copy Markdown
Member

@nprigour feel free to add a new comparison method, the current one was clearly broken code wise, the class comparison was incorrect.

@nprigour

nprigour commented Oct 8, 2019

Copy link
Copy Markdown
Contributor

Hi @aaime,
Do I need to create first a new JIRA issue or is it sufficient to proceed directly with the creation of a new PR to address this?

@aaime

aaime commented Oct 8, 2019

Copy link
Copy Markdown
Member

Can you please create a Jira ticket? We use Jira to create the release notes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants