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

From John Turner
Subject Re: [GENERAL] Imperative Query Languages
Date
Msg-id CAMAP1Q=UYOMoixnBv8Qh9HefB29Pqjx4cTa7EBZjUjR7DC0i9A@mail.gmail.com
Whole thread Raw
In response to [GENERAL] Imperative Query Languages  (Jason Dusek <jason.dusek@gmail.com>)
List pgsql-general
(copying the list)

On Wed, Jul 5, 2017 at 12:22 AM, Jason Dusek <jason.dusek@gmail.com> wrote:

Are there any “semi-imperative” query languages that have been tried in the past? 

not particularly relevant to the Unix or Windows worlds, but on OpenVMS there's Datatrieve:

-John

On Wed, Jul 5, 2017 at 12:22 AM, Jason Dusek <jason.dusek@gmail.com> wrote:

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: Mayank Agrawal
Date:
Subject: [GENERAL] (Might be a bug) locale issue while upgrading data directory fromPostgreSQL 8.4 to 9.5
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Imperative Query Languages