Once complete Hibernate mappings/integration is done for OpenNMS
(on of the Summer of Code projects) one should be able to hackaround with
either hibernate mappings or Spring's AOP (aspects) to do some thing with
the transaction management at the core to store stuff to two databases.
But we h
Steven Turner wrote:
> Hi DJG, thanks for the reply I'm only wanting to use one instance of OpenNMS
> which uses only one database but I'm wanting all the information from the
> first database to be mirrored in the second database so that every time the
> 1st database is updated in some way this
Hi DJG, thanks for the reply I'm only wanting to use one instance of OpenNMS
which uses only one database but I'm wanting all the information from the first
database to be mirrored in the second database so that every time the 1st
database is updated in some way this information is copied over t
Why do you want to do what you mentioned? What are your functional
requirements?
In short: you most likely don't want to do what you are asking about.
There would be a high amount of effort invested to make such a change
it will have nasty architectural, performance, and data consistency
Hi,
I'm wanting to make a duplicate of the OpenNMS database which is residing on
the same server but with an additional column attached to all tables which has
its content generated by a function. This duplicate database will have excatly
the same SQL querys performed on it as the original Op
