Implementing State Machines in PostgreSQL

Re:Implementing State Machines in PostgreSQL by justQuestion2 on Monday July 31, 2017 @11:29AM (#14892882)

I found it hard to use entities with more than 4 Attributes when defining them as simple compounds like

person(Firstname, Lastname, Gender, Age, State, Country).

Accessing the attributes by position makes the code hard to read because one has to remember the position and mistakes are not catched because there is no type system.

Would you recommend using the libray record or using dicts in swi-prolog? This would make the code non portable. Moreover, do you recommend dedicated strings or list of atoms to represent strings?

[ Parent | on HN ]

Re:Implementing State Machines in PostgreSQL by NotAUsername on Monday July 31, 2017 @01:12PM (#14893881)

Hey! Grakn person here.

The Prolog syntax is very elegant but it could be clunky, I totally agree. Our syntax has resource and role names instead of relying on position:

e.g.

match $x has lastname "some last name";

[ Parent | on HN ]