On Jul 5, 2010, at 8:57, Mattias Persson wrote: > Maybe there's some bug in the removeIndex(Node,String) method. Instead > try to do a: > > index.removeIndex(classNode1,MetaModelProperty.KEY_NAME,classNode1.getName()); > > before you set the new name
I've tested this already. Indexing works OK. The problem is in namespace.getMetaClass() > What is your use case for renaming a meta model class? Is that really > functionality that should be used at runtime? My gut feeling says that > this is a develpment time thing and once a class is created with a > name it sticks with that name. Or are you doing some kind of migration > of your data? Renaming a class is required when building a graphical modelling tool. That is, the user creates classes and properties and he want to rename them. This happens at runtime. I'm currently working on a rewrite of the DeepaMehta open source project. DeepaMehta is a platform for collaboration and knowledge management. In existence since 10 years, 6 years in production. Part of DeepaMehta is a modelling feature. For the DeepaMehta rewrite I switched from MySQL to CouchDB, and now to Neo4j. Neo4j fits the DeepaMehta model very well and Neo4j storage runs smooth since 2 months. Now, while working on the modelling feature I hit the wall at meta-model component. I would love to release DeepaMehta 3 v0.4 (the first version based on Neo4j) soon. Is there a reason to not have a setName() method on MetaModelObject? Cheers Jörg _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
