I don#t know why you should lose references? This appear likely more than a UI problem (UI for managing 200 references might require custom coding). In addition: you backup your data on a regular basis and if you really don't trust Plone/Zope/ZODB: write a script exporting the reference information into a textual format (trivial).
-aj On Mon, Dec 21, 2009 at 11:46, Simone Orsi <[email protected]> wrote: > Hi list, > > I have to develop a product which has two archetypes: one > "container_object" which can be considered as a big "false" container > and one which can be considered as a simple_object to be related to the > container_object. > > I can't make the container_object a real container, such as a folder, > because I need to create a lot of container_objects that can relate the > same simple_objects' set. > > When the user creates a container_object I want him/her to be able to > assign to it as many simple_objects as he/she wants. The number of > related simple_objects can vary from 15 to 200+. The view of the > container_object will show the list of all the simple_objects related to > it. > > My question is: will be reliable a referenceField with such number of > relations? I'm a bit scared about the ease of losing objects' relation. > In my case would mean a real catastrophe :( > > Is a referenceFied the way to go? > > TIA, > SimO > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers >
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
