Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-Id: <E0691BE4-05A4-4D7D-A5A4-584270873F11@objectstyle.org>
From: Andrus Adamchik <andrus@objectstyle.org>
To: user@cayenne.apache.org
In-Reply-To: <20090512101102.AA38.60BA733C@jeremias-maerki.ch>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Interfaces for domain objects?
Date: Wed, 13 May 2009 13:19:14 -0400
References: <20090512101102.AA38.60BA733C@jeremias-maerki.ch>


On May 12, 2009, at 4:40 AM, Jeremias Maerki wrote:

> While I'm at it: Can I ask why DeleteQuery has been deprecated? I'd
> rather use that instead of EJBQLQuery. Not having to concatenate  
> strings
> to build queries is one of the features that makes Cayenne appeal to  
> me
> so much. I've had stuff like that back in my Delphi times and I liked
> that very much.


The problem with DeleteQuery (or EJBQL delete for that matter) is that  
it didn't clean up in-memory objects that were deleted in the DB. So  
the feeling was that it is conceptually wrong as a public user API.  
The preferred way is get a hold of an object and do  
context.deleteObject(..).

Of course the need for a batch delete operation doesn't completely go  
away with the above. I guess we may need to work on getting it right  
as a part of the planned post 3.0 effort to merge redundant queries  
together and provide them all with a non-String OO creation interface.

Andrus