Hi Bruno, The "best" way would depend on what your data looks like. Often you can use the regular Java serialization and just save "somewhere" instead of a database if you just need to store things for a little bit. If you need to persist between sessions, then you could flatten your tree and simply save the data as rows in a table. The trick is to get able to reconstruct the outline structure, so you would have to save the nesting level of each node.
How is your data loaded in the first place? This would be a good place to start to decide how to persist it. If you just need to save the data "for a second" in order to build another tree while the application is still running, you really don't have to do anything - just take the tree data from the first tree and call "setTreeData" with the same stuff in the second tree. It would help if you could provide some more detail about what kind of object(s) you are using for your tree data and how it is loaded to begin with. Thanks for using Pivot! ~Roger Whitcomb From: Bruno Rodrigues [mailto:[email protected]] Sent: Monday, April 23, 2012 8:25 AM To: user Subject: best way to save a treeview state into the database Hello, guys. simple question: what is the best way to persist an especific treeview data in a database, to retrieve it after to build another tree? Thanks
