On Feb 18, 2005, at 2:14 AM, Lane Sharman wrote:
merge has got to be one of the weirdest choices conceived in all my
years of writing code to describe a save operation.
It doesn't save, it merges state. It's fine, save/update are not really
great in this context, but we need them.
--
Christian B
Christian Bauer wrote:
Christian Bauer wrote:
Starting with H3, we recommend the new EJB3-style operations create()
and merge().
merge has got to be one of the weirdest choices conceived in all my
years of writing code to describe a save operation.
-Lane
-
My view is that this is a major version update and we are aligning with
a standard so we should change APIs to suite as well as behaviour.
+1
Cheers David.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Christian Bauer
Sent: Monday, 14 February 200
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:hibernate-devel-
> [EMAIL PROTECTED] On Behalf Of Emmanuel Bernard
> Sent: Monday, February 14, 2005 3:16 AM
> To: hibernate-devel@lists.sourceforge.net
> Subject: Re: [Hibernate] Re: API name changes
>
>
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
