A while ago I highlighted a problem with the differences between the documented API and what Hibernate actually does and I'm seeking to an open discussion about the merits and problems to renaming the current #replicate() function to #replicateOrSave() to better identify what it actually does.
This is so that a hole can be left open to implement a real #replicate() function which makes contact guarantees that the primary key / OID will be identical even in IDENTITY tables in the replicated object or otherwise it throws an exception. There should also be a feature enquiry function to allow the API programmer to ask the underlying Hibernate implementation to verify if a replication on identity table will work. This would account for JDBC driver vendors and versions and the realtime SQL database server vendor and version. http://www.mail-archive.com/hibernate-devel@lists.sourceforge.net/msg05230.html http://forum.hibernate.org/viewtopic.php?t=949574&highlight= http://www.hibernate.org/hib_docs/v3/api/org/hibernate/Session.html#replicate(java.lang.Object,%20org.hibernate.ReplicationMode) RFC Darryl ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
