SQL++ for Mobile — Differences from SQL++ for Server

SELECT fname, email FROM tutorial USE KEYS ("dave", "ian");

SELECT fname, email FROM tutorial WHERE meta().id IN ("dave", "ian");

SELECT * FROM user u
JOIN orders o ON KEYS ARRAY s.order_id FOR s IN u.order_history END;

SELECT * FROM user u, u.order_history s
JOIN orders o ON s.order_id = meta(o).id;

SELECT * FROM user u
JOIN orders o ON KEY o.user_id FOR u;

SELECT * FROM user u
JOIN orders o ON meta(u).id = o.user_id;

SELECT * FROM user u
NEST orders orders
ON KEYS ARRAY s.order_id FOR s IN u.order_history END;

NEST/UNNEST not supported

SELECT * FROM user u
LEFT OUTER NEST orders orders
ON KEYS ARRAY s.order_id FOR s IN u.order_history END;

NEST/UNNEST not supported

ARRAY i FOR i IN [1, 2] END

(SELECT VALUE i FROM [1, 2] AS i)

ARRAY FIRST arr

arr[0]

Allows OFFSET without LIMIT

Allows OFFSET without LIMIT

All three are supported (with ALL and DISTINCT variants)

Not supported

Both LEFT and RIGHT OUTER JOIN supported

Only LEFT OUTER JOIN supported (and necessary for query expressability)

Can compare either complex values or scalar values

Only scalar values may be compared

Result sequencing is based on specific rules described in SQL++ (server) OrderBy clause

Result sequencing is based on the SQLite ordering described in SQLite select overview

The ordering of Dictionary and Array objects is based on binary ordering.

Supported

SELECT DISTINCT VALUE is supported when the returned values are scalars

Supported

Not Supported

Supported

Not Supported