The SQL standard: Where does it come from? Where does it go?

Peter Eisentraut

peter@eisentraut.org
@petereisentraut

About me

Starting from the top …

Coming together …

We are here

What happens where

Participating

ISO members are “national bodies” (NB):

National mirror committees

for JTC1 SC32:

How you end up in WG3

How you end up in SC32

Who participates where

WG3 meetings

Current/recent WG3 meetings

WG3 officers

WG3 projects

How to make a change

  1. Write a change proposal (“paper”)
  2. Upload it to ISO CMS
  3. Present it at meeting
  4. Discussion
  5. Paper gets accepted or not
  6. If accepted, editor integrates it into draft

example paper

Project progression

  1. NWIP
  2. WD
  3. CD
  4. DIS
  5. (FDIS)
  6. IS

Project progression

  1. NWIP
  2. WD
  3. CD (SC32 votes)
  4. DIS (JTC1 votes)
  5. (FDIS) (JTC1 votes)
  6. IS (publication)

Current status of 9075

What is new in SQL:202x

SQL:202x: SQL/PGQ

(new part 16)

SELECT gt.creation_date, gt.content
FROM my_graph GRAPH_TABLE (
  MATCH
    (creator IS person WHERE creator.email = 'foo@example.com')
      -[ IS created ]->
    (m IS message)
      <-[ IS commented ]-
    (commenter IS person)
    WHERE creator.email <> commenter.email
    COLUMNS (m.creation_date, m.content)
) AS gt;

(more detailed presentation)

SQL:202x: more JSON stuff

SQL:202x: various smaller bits

SQL:202x: various smaller bits

SQL:202x: various smaller bits

What’s in the future?

Terminology aid

SC32/WG3 PostgreSQL
working draft (WD) Git HEAD
committee draft (CD) beta
draft internal standard (DIS) release candidate
WG3 hackers
SC32 PGCon developer meeting
change proposal paper patch
meeting commit fest
editor committer

Conclusion