• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Handy SQL join explanation"

Collapse

  • NickFitz
    replied
    I was referring to standard SQL, not SQL with a bunch of proprietary extensions.

    Leave a comment:


  • Spacecadet
    replied
    Originally posted by NickFitz View Post
    Of course XSLT is Turing-complete, which SQL isn't
    http://assets.en.oreilly.com/1/event...esentation.pdf

    Leave a comment:


  • NickFitz
    replied
    Set theory is also crucial to understanding XSLT (the clue is in the constant references to "node sets" in the specs) yet hardly anybody using the language seems to understand that... then again, they don't understand the implications of it being a declarative language (as is SQL) either.

    Of course XSLT is Turing-complete, which SQL isn't, so that probably confuses them as they develop complex ways to do stuff that would be simple if they knew what to do with sets.
    Last edited by NickFitz; 29 April 2010, 04:54.

    Leave a comment:


  • Zippy
    replied
    Originally posted by Spacecadet View Post
    Maybe (just maybe) basic set theory should be explained before they are let anywhere near a database.
    We did that at school and I still draw Venn diagrams sometimes

    Leave a comment:


  • Spacecadet
    replied
    Originally posted by Moscow Mule View Post
    I know this won't be of much use to you hardened SQL warriors out there, but I just found this link which I found very helpful in explaining joins to one of our developers.

    Coding Horror: A Visual Explanation of SQL Joins
    Maybe (just maybe) basic set theory should be explained before they are let anywhere near a database.

    Leave a comment:


  • suityou01
    replied
    Originally posted by Moscow Mule View Post
    I know this won't be of much use to you hardened SQL warriors out there, but I just found this link which I found very helpful in explaining joins to one of our developers.

    Coding Horror: A Visual Explanation of SQL Joins
    Since SQL joins appear to be set-based


    Good article though

    Leave a comment:


  • Cliphead
    replied
    Originally posted by Moscow Mule View Post
    I know this won't be of much use to you hardened SQL warriors out there, but I just found this link which I found very helpful in explaining joins to one of our developers.

    Coding Horror: A Visual Explanation of SQL Joins
    That's useful. I'm currently trying to get my head around SQL so I can create ad hoc reports.

    Leave a comment:


  • Moscow Mule
    started a topic Handy SQL join explanation

    Handy SQL join explanation

    I know this won't be of much use to you hardened SQL warriors out there, but I just found this link which I found very helpful in explaining joins to one of our developers.

    Coding Horror: A Visual Explanation of SQL Joins
Working...
X