XTM 1.0 Synchronize Update API not populating values in "reified_id" column in many tables #88

Closed
GoogleCodeExporter opened this Issue Mar 16, 2015 · 4 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
we've tested Synchronize update of XTM file into database which contains 
two associations(duplicate) and corresponding two reified topics using 
TopicMapSynchronizer.update() API but all reified_id columns in many 
tables contains NULL values.


Original issue reported on code.google.com by joeprad...@gmail.com on 20 Jul 2009 at 5:18

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 16, 2015

Original comment by lar...@gmail.com on 20 Jul 2009 at 5:23

  • Changed state: Accepted
  • Added labels: Component-Engine, TMSync

Original comment by lar...@gmail.com on 20 Jul 2009 at 5:23

  • Changed state: Accepted
  • Added labels: Component-Engine, TMSync
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 16, 2015

The problem here is that Synchronize does not consider the reifying topic to be 
part 
of the set of topics to synchronize, and so leaves it out, thus losing the 
reification.

The best way to approach this seems to be to ask the decider whether or not to 
include the reifier, and if the answer is yes to synchronize it in the usual 
way.

Original comment by lar...@gmail.com on 22 Jul 2009 at 8:51

The problem here is that Synchronize does not consider the reifying topic to be 
part 
of the set of topics to synchronize, and so leaves it out, thus losing the 
reification.

The best way to approach this seems to be to ask the decider whether or not to 
include the reifier, and if the answer is yes to synchronize it in the usual 
way.

Original comment by lar...@gmail.com on 22 Jul 2009 at 8:51

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 16, 2015

Fixed by revision 358, I hope.

Original comment by lar...@gmail.com on 22 Jul 2009 at 9:31

  • Changed state: Fixed
Fixed by revision 358, I hope.

Original comment by lar...@gmail.com on 22 Jul 2009 at 9:31

  • Changed state: Fixed
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 16, 2015

Original comment by lar...@gmail.com on 1 Sep 2009 at 11:54

  • Added labels: Release5.0.1

Original comment by lar...@gmail.com on 1 Sep 2009 at 11:54

  • Added labels: Release5.0.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment