On Sun, 2002-09-22 at 09:34, Thomas Mahler wrote: > Hi again, > > <snip> > >> > >> Forcing a cascading delete on all children in the collection, > >> whether or not OJB has retrieved them in the past (yes, you > >> will be issuing a potentially useless delete, but I have > >> explicitly given you the go-ahead with the "always" flag). > > > > > > Now I get your idea. > > > > I propose the following: > > To get started with such a mechanism we first need a way to delete by > > query. > > We can add a method deleteByQuery(Query) to the PB Interface. > > This will allow to delete the N-side objects without materializing them. > > > > This feature will be useful for everyone, easy to implement and work as > > first workaround for your problem. > > > > Yesterday I implemented PB.deleteByQuery(Query) and commited it to CVS. > So if you are eager to experiment with this feature you can already use it!
Excellent! Great news. Thanks. -scott -- Scott C. Gray <[EMAIL PROTECTED]> | Quidquid latine dictum sit, altum Director of Engineering, MWS | videtur -- Whatever is said in (V) 856-914-5212 | Latin sounds profound. (F) 856-608-7970 | -Unknown -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
