From: Khalil A. <ka...@te...> - 2004-11-09 13:32:27
|
Hi Andy, Currently the code doesn't clean up unused locators. The issue is that the data model allows a locator to be referenced as the value of an occurrence, as a subject indicator, a subject address, a source locator or a topic map base locator and potentially there could be other references to the same object. I guess I could add code to check if a locator is unused and remove it from the database in that case. This would potentially slow down some property changes (if it requires an additional lookup to check if the removed/modified locator is now unused) but it might be beneficial in topic maps with a high rate of churn (e.g. new topics being regularly imported and then destroyed). Can you add a bug report to the tracker for this please ? Cheers, Kal On 9 Nov 2004, at 06:51, Andy Peel wrote: > Hello, > > I have a topic map for which I've changed the base locator using: > > org.tm4j.topicmap.TopicMap.setBaseLocator(Locator base) > > However, this leaves a row in the locator table (I'm using Hibernate) > for > the old locator. > > Is there a way to remove the old locator? > > Thanks, > > > Andy. > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Tm4j-developers mailing list > Tm4...@li... > https://lists.sourceforge.net/lists/listinfo/tm4j-developers > > |