I am not completely sure he is talking about replication. Lets say you have an employee record on the server, the server sends the record to the client application who then changes the phone number. The record is returned to the server from the client changed. The server now needs to set the record in the database. Now, obviously, you can locate the object, replace the changed attributes and commit the change or, i think what he asks, merge the changes in some way the SA engine provides. Also note that the record is actually an SA object that was de/serialized and not arbitrary fields.
I have a feeling that as long as you keep the session open just committing the object should work. However, i think there are larger issues here. If the object was at the client you cannot trust it security wise, you need to have a mechanism that will ensure sanity. Either manually or automatically by SA. On Wednesday 12 July 2006 21:28, Jonathan Ellis wrote: > On 7/12/06, Steve Zatz <[EMAIL PROTECTED]> wrote: > > I am trying to find the most efficient way to keep two databases in > > sync. > > What is the difference between what you are trying to do and replication? > Replication should really be handled at a lower level than SA. Most modern > DBs have a replication solution available. -- Regards, Tzahi. -- Tzahi Fadida Blog: http://tzahi.blogsite.org | Home Site: http://tzahi.webhop.info WARNING TO SPAMMERS: see at http://members.lycos.co.uk/my2nis/spamwarning.html ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
