I have a setup with an RDBMS topic map (RDBMSTopicMapSource), not read-only.
Modifying this topic map using tolog updates via the Omnigator plug-in has no
effect at all. If I delete a topic, for example, it's still there after the
request has finished.
The plug-in code calls commit() so this is not the reason. I've also verified
that TopicIF.remove() is being called on the topic. Printing debug info shows
that the topic map and transaction have readonly = false.
I'm stumped. It would be great if we could fix this because being able to do
modifications like this is extremely useful.
Original issue reported on code.google.com by lar...@gmail.com on 10 Aug 2010 at 10:49
The text was updated successfully, but these errors were encountered:
It was suggested that the problem was that the transaction was read-only (even
though tests showed it was not). As of revision 1310 the transaction is now
explicitly set to read-only/not readonly depending on whether an updated is
Updates still have no effect whatsoever.
Original comment by lar...@gmail.com on 25 Aug 2010 at 9:02