TypeQL 3.0

[dmitrii-ubskii]

Usage and product changes

User-defined functions and structs:

fun mean_salary($c: company) -> double? :
    match 
        (company: $c, employee: $_) isa employment, has salary $s;
    return mean($s); 

struct dated_coordinate:
    longitude value double,
    latitude value double,
    date value datetime;

Query pipelines:

with fun costliest_printer($employee: employee) -> printer? :
  match 
    ($printer, $employee) isa print_permission;
    $printer has cost_per_page $cost;
  sort $cost desc;
  return first($printer);
match
  $printer isa printer, has office_number $n, has newly_installed true;
  $employee isa employee, has office_number $n;
put ($employee, $printer) isa print_permission;
match 
  $high_cost_printer = costliest_printer($employee), has printer_name $name;
  not { $printer is $high_cost_printer; };
  $employee has contact $address;
insert 
  $notice isa queued_email, has recipient $address, 
  has content "Do you still need the printer " + $name + "?";

New undefine syntax allows user to be more precise as to what is being undefined:

undefine
owns age from person;
@regex from first-name;
as name from person owns first-name;

New, more concise delete syntax:

match $p isa person, has name $n;
delete $n of $p;

Implement JSON-like string unescaping (closes #106).

See The TypeDB 3.0 Roadmap for more details!

[flyingsilverfin]

Let's make sure this is outlined in the PR description + we can close the long-lived open PR if it is solved!