[GENERAL] Imperative Query Languages - Mailing list pgsql-general

From Jason Dusek
Subject [GENERAL] Imperative Query Languages
Date
Msg-id CAO3NbwPcwwYBPHDPpvnT4iQPaO8kuOrBLxd1tSHiT137z9+CCA@mail.gmail.com
Whole thread Raw
Responses Re: [GENERAL] Imperative Query Languages  (John Turner <fenwayriffs@gmail.com>)
Re: [GENERAL] Imperative Query Languages  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [GENERAL] Imperative Query Languages  (Chris Travers <chris.travers@gmail.com>)
Re: [GENERAL] Imperative Query Languages  (Merlin Moncure <mmoncure@gmail.com>)
Re: [GENERAL] Imperative Query Languages  (Christopher Browne <cbbrowne@gmail.com>)
List pgsql-general

Hi All,

This more of a general interest than specifically Postgres question. Are there any “semi-imperative” query languages that have been tried in the past? I’m imagining a language where something like this:

for employee in employees:   for department in department:       if employee.department == department.department and          department.name == "infosec":           yield employee.employee, employee.name, employee.location, employee.favorite_drink

would be planned and executed like this:

SELECT employee.employee, employee.name, employee.location, employee.favorite_drink FROM employee JOIN department USING (department)WHERE department.name == "infosec"

The only language I can think of that is vaguely like this is Fortress, in that it attempts to emulate pseudocode and Fortran very closely while being fundamentally a dataflow language.

Kind Regards,

  Jason

pgsql-general by date:

Previous
From: Chris Travers
Date:
Subject: [GENERAL] Strange case of database bloat
Next
From: Mayank Agrawal
Date:
Subject: [GENERAL] (Might be a bug) locale issue while upgrading data directory fromPostgreSQL 8.4 to 9.5