Dear Monks,

I have been watching a series of Advanced SQL lectures online.

Most my experience with SQL is with 1992 standards. I used T-SQL for MS SQL Server.

I'm quite impressed with some of the new functions of more recent standards. Others I'm not so sure about. It seems to me that much of the recent additional functionality could be achieved using simpler code, admittedly longer code (as was with SQL-92). Compactness of code seems to me to be unimportant relative to clarity.

Much could be achieved, I remember, interfacing Perl code with T-SQL. Is SQL in danger of running ahead of itself? Should SQL be contained and constrained? I kind of feel that much can be achieved using SQL, including class inheritance. But how far should the SQL ISO standards go with all that?

SQL is now a Turing complete declarative language, with a recursion capability.

Any thoughts on all that?


Update___________

My thinking has been that programming languages do not quite adequately consider the requirements of Agile methodology. This became clear when reviewing the recent implementations of SQL for the various DMS.

In reply to [OT] Reflecting on SQL. Meditating on Perl. Do languages meet requirements of Agile? by betmatt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.