I have two master databases. One on the web, one on the user side. Both are master sources (ie. both are updated and should contain all information). Does the framework allow me to synchronize these two databases?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Basically I just need to do a master to master replication during the synchronization.
You referred to "roll your own" solution... any tips regarding this matter. I have not done a similar project of this sort.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's not really something I want to delve into too deeply here, and you need to decide if you are doing one-way or two-way synchronisation.
2-way is a lot more difficult as you need to deal with some complex issues. For example if a record is deleted on one database while the same record is updated in the other database then which change is the one to keep? what happens with referential integrity etc if that change also affected a number of other tables? Should you be recplicating transactions or records? etc.
Your best guide in terms of how you would do this would be to find a good book on database theory and get ideas from there.
Sorry I can't be a more helpful, but the subject is very complex and not really one I want to tackle in a forum environment.
Maybe you can also check google for replication usijng your specific database system - there could already be a solution out there.
- Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two master databases. One on the web, one on the user side. Both are master sources (ie. both are updated and should contain all information). Does the framework allow me to synchronize these two databases?
Sorry, No.
While the framework does allow you to use objects persisted to either database, it doesn't do DB synchronization.
There's just way too many issues to have a single solution that provides this for multiple database sources - at least, for me there is ;-)
I think that synchronization, distributed transactions, etc are features that are best left to your specific database engine to provide.
There are ways to do a "roll your own" solution if the database doesn't provide what you need.
Feel free to give me more information and maybe I can give you some tips.
- Richard
Thank you for your quick reply.
Basically I just need to do a master to master replication during the synchronization.
You referred to "roll your own" solution... any tips regarding this matter. I have not done a similar project of this sort.
It's not really something I want to delve into too deeply here, and you need to decide if you are doing one-way or two-way synchronisation.
2-way is a lot more difficult as you need to deal with some complex issues. For example if a record is deleted on one database while the same record is updated in the other database then which change is the one to keep? what happens with referential integrity etc if that change also affected a number of other tables? Should you be recplicating transactions or records? etc.
Your best guide in terms of how you would do this would be to find a good book on database theory and get ideas from there.
Sorry I can't be a more helpful, but the subject is very complex and not really one I want to tackle in a forum environment.
Maybe you can also check google for replication usijng your specific database system - there could already be a solution out there.
- Richard