On 7/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

lateef jackson wrote:
> Is it possible to send all insert and updates to multiple database backends?
> There is still an issue with getting databases that have failed back in
> sync. Just an idea for shortest path.

Use the database server's replication.  Trying to send manage updates
to several databases through your application will inevitably lead to
failure when the updates get issued in different orders on the
different servers.  (Imagine if you're saving two new objects at the
same time.  The inserts may not happen in the same order on both
databases so the objects have different ids on each database.  Any
related records inserted will be broken on one of the databases because
the ids are inconsistent.)

http://c-jdbc.objectweb.org/  - Is an implementation in Java

Sequence generation is pretty easy work around. you can have your own sequence generator code as explain here:
http://c-jdbc.objectweb.org/current/doc/userGuide/html/ar01s05.html#using_sequence_with_hibernate
There are many other sequence generation cluster options if you do some googling. There are many more painful issues than sequence generation. Recovery being the one that stands out most to me. I don't like how CJDBC resolves this I like the way slony-i in PostgresSQL does by queueing up updates. Just mulling it over, it could be a fun experiment.



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to