<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
Hey Alan,<br>
<br>
thanks a lot.<br>
The #beExclusive message did the job. I wasn't aware of the glorp<br>
mailing list, but I definately dig into it.<br>
<br>
Thanks again,<br>
Peter<br>
<br>
Alan Knight schrieb:<br>
<span style="white-space: pre;">> Note that there is a Glorp
mailing list hosted at sourceforge,<br>
> which is probably a better option for finding Glorp-specific<br>
> answers.<br>
> <br>
> Glorp does not have the ability to take advantage of the
database's<br>
> built-in cascading delete. The primary issue is that the objects
in<br>
> memory won't get told about the deletions that have happened in
the<br>
> database and so things will get out of sync. If you don't care<br>
> about that (e.g. because you're going to throw away the objects
in<br>
> memory right away after the delete anyway) then you could set up<br>
> cascaded delete in tables as you would normally.<br>
> <br>
> If you're willing to let Glorp do the cascading (less efficient,<br>
> but better control) then you can do this by sending the message<br>
> #beExclusive to the mappings that you want to cascade.<br>
> <br>
> Taking advantage of update cascade seems to mean that you'd be<br>
> changing the primary key of the object. I think that would be
very<br>
> likely to cause any number of interesting problems, and I'd think<br>
> long and hard before trying to do that from within Glorp. At a<br>
> minimum, it's going to mess up the caching, which is based on<br>
> primary keys, and you'd want to discard the session immediately.<br>
> <br>
> At 03:52 AM 12/4/2008, Peter Osburg wrote: Hi list,<br>
> <br>
> I am looking for a solution to define a cascaded update and
delete<br>
> on a field. Unfortunately I can't find a solution. It would be<br>
> great to get some help on the problem.<br>
> <br>
> Thanks in advance, Peter<br>
>> </span><br>
_______________________________________________<br>
seaside mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br>
<span style="white-space: pre;">> -- Alan Knight [|], Engineering
Manager, Cincom Smalltalk <br>
> <a class="moz-txt-link-abbreviated" href="mailto:knight@acm.org">knight@acm.org</a> <a class="moz-txt-link-abbreviated" href="mailto:aknight@cincom.com">aknight@cincom.com</a> <a class="moz-txt-link-freetext" href="http://www.cincom.com/smalltalk">http://www.cincom.com/smalltalk</a><br>
<br>
> -------------------------<br>
<br>
> _______________________________________________ seaside mailing<br>
> list <a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a> <br>
>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a></span><br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v1.4.9 (MingW32)
<br>
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a>
<br>
<br>
iEYEARECAAYFAkk4/uMACgkQ0qdvZsCNFKGKygCgokSI3Wtoottp8oyDYmMziokx
<br>
hoAAoLArcnP4HpOrNPpfxLJRV/X6iUiQ
<br>
=dc18
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>