Christian Bauer wrote:
Christian Bauer wrote:
Starting with H3, we recommend the new EJB3-style operations create() and merge().
We still have our old methods: save(), update(), saveOrUpdate(), with slightly different semantics. What do you think about save(), attach(), saveOrAttach()? It might be too much code to change, but this is really our last chance to fix it and to help people think in object states, not SQL statements (something I repeat about 10 times during a Hibernate training).
'save' and 'attach' seems not coherent with each other, I'm not a big fan.
Again, I repeat this question. It's critical for our docs, training material, etc. Repeat: This is the last chance to make any changes. Even if you don't really have much to say about it, express your opinion please.
Also, should we rename create() to persist() to be aligned with EJB3 EDR2?
+1
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
