Thank you! Highly appreciating that :-) I'm looking forward ...
Cheers Jörg On Jul 5, 2010, at 17:54, Niels Hoogeveen wrote: > If Mattias agrees, I suggest adding the methods: > MetaModelNamespace#rename(String oldName, String newName) > MetaModelNamespace#remove(String name, Boolean forced) > If forced is false, throw exception when relations exist to other > MetaModelObjects or in case of a MetaModelClass, has associated instances. If > forced is true, all relationships are removed together with the > MetaModelObject. > I am willing to make the changes, but want approval from the Neo4J team > before making these adjustments. > Niels >> From: [email protected] >> Date: Mon, 5 Jul 2010 13:54:10 +0200 >> To: [email protected] >> Subject: Re: [Neo4j] Meta-model component: problem with renaming classes >> >> >> On Jul 5, 2010, at 9:13, Niels Hoogeveen wrote: >> >>> MetaModelClasses are cached in a map, so while the property may be renamed >>> and reindexed, the map still holds the original name value. After a restart >>> of the application the new value should be applied. To make renaming >>> possible a method needs to be added to MetaModelNamespace. >>> Niels >> >> Thank you for the info! >> Restarting the application is not an option in dynamic environments, where >> classes come and go (and change their names) at runtime. >> BTW: deleting a class is also an issue with the meta-model component. >> >> Is it possible for you to add a setName() method to MetaModelObject (or >> elsewhere)? >> >> This would allow developers to use the meta-model component in dynamic >> applications. >> >> Cheers >> Jörg _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
