<div dir="ltr"><br><br><div class="gmail_quote">2008/7/17 <<a href="mailto:ihab.awad@gmail.com">ihab.awad@gmail.com</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><br><div class="gmail_quote"><div class="Ih2E3d">On Thu, Jul 17, 2008 at 11:03 AM, Jonathan S. Shapiro <<a href="mailto:shap@eros-os.com" target="_blank">shap@eros-os.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Equally important, it constitutes an alleged type system that informally<br>
encapsulates many of the essential internal semantic relationships of<br>
the data set, and the transactional capabilities of a DBMS mean that you<br>
can do an all-or-nothing upgrade procedure on it.<br>
</blockquote></div><div><br>Interesting. The argument on the other side, of course, is that people miss having Turing complete semantics to express the invariants and internal relationships within that alleged type system. Hence database triggers (horror!) and PL/SQL (septuple horror!).<br>
</div></div></div></blockquote><div><br>What's wrong with database triggers?<br> <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="gmail_quote"><div><br>What if one were to adopt the same sort of architecture, but consider the "database" to be -- well -- a large vat with relatively simple semantics. Upgrade it all in one big turn and we're done, and write its clients such that they can be "rebooted" easily. Maybe orthogonal persistence is a sharp knife to be used wisely.<br>
<br>Ihab<br><br></div></div>-- <br>Ihab A.B. Awad, Palo Alto, CA
</div>
<br>_______________________________________________<br>
cap-talk mailing list<br>
<a href="mailto:cap-talk@mail.eros-os.org">cap-talk@mail.eros-os.org</a><br>
<a href="http://www.eros-os.org/mailman/listinfo/cap-talk" target="_blank">http://www.eros-os.org/mailman/listinfo/cap-talk</a><br>
<br></blockquote></div><br></div>