Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

Allow customized strategy in case labels (or relationship types) have same name but different cases #11

Open
santo-it opened this issue Dec 29, 2016 · 0 comments
Assignees
Milestone

Comments

@santo-it
Copy link

santo-it commented Dec 29, 2016

With current version, 2.2.14:

  • Neo4j Nodes with same Label but different case, e.g. LABEL and LAbel will be aggregated into a single OrientDB vertex Class
  • Neo4j Relationship with same name but different case, e.g. relaTIONship and RELATIONSHIP will be aggregated into a single OrientDB edge Class

This is an enhancement request to allow users to customize the strategy. The above can be one strategy, but other strategies are possible, e.g. append a random string to the label or relationship type, and migrate them into separated classes

This seems to be not a common case - but could be useful to improve how we behave here anyway

@santo-it santo-it self-assigned this Dec 29, 2016
@santo-it santo-it added this to the 3.0 milestone Dec 29, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant