Hasura auto-generates a complete GraphQL API from your PostgreSQL schema — including queries, mutations, subscriptions, and permissions. UUID v7 primary keys integrate seamlessly: set a database-side default, and Hasura’s generated API automatically handles ID generation, chronological sorting, and cursor pagination. See PostgreSQL 18 Native UUID v7 for the PostgreSQL setup.

PostgreSQL schema with UUID v7 default

-- PostgreSQL 18 — native UUID v7
CREATE TABLE orders (
  id          UUID PRIMARY KEY DEFAULT gen_random_uuid_v7(),
  customer_id UUID NOT NULL,
  total       NUMERIC(10, 2) NOT NULL,
  status      TEXT NOT NULL DEFAULT 'pending',
  -- No created_at needed — UUID v7 id encodes creation time
  FOREIGN KEY (customer_id) REFERENCES customers(id)
);

-- PostgreSQL 15-17 — pg_uuidv7 extension
-- CREATE EXTENSION IF NOT EXISTS pg_uuidv7;
-- ALTER TABLE orders ALTER COLUMN id SET DEFAULT uuid_generate_v7();

After running this migration, connect Hasura to your PostgreSQL database and track the table.

Hasura auto-generated GraphQL

Hasura generates these operations automatically from the schema above:

Insert (Hasura omits id from input — uses PostgreSQL default)

mutation CreateOrder($customerId: uuid!, $total: numeric!) {
  insert_orders_one(object: {
    customer_id: $customerId
    total: $total
  }) {
    id          # UUID v7 generated by PostgreSQL
    status
  }
}

Query — chronological order via UUID v7

query ListOrders($limit: Int!, $cursor: uuid) {
  orders(
    order_by: { id: asc }
    limit: $limit
    where: { id: { _gt: $cursor } }
  ) {
    id
    customer_id
    total
    status
  }
}

order_by: {id: asc} with UUID v7 is equivalent to ordering by creation time. See UUID v7 for Cursor Pagination.

Subscription — real-time ordered updates

subscription WatchOrders($customerId: uuid!) {
  orders(
    where: { customer_id: { _eq: $customerId } }
    order_by: { id: asc }
  ) {
    id
    total
    status
  }
}

UUID v7 subscriptions deliver events in chronological insertion order — the newest record always has the highest UUID value.

Hasura permission rules with UUID v7

# hasura/metadata/databases/default/tables/public_orders.yaml
select_permissions:
  - role: user
    permission:
      columns: [id, customer_id, total, status]
      filter:
        # Users can only see their own orders
        customer_id:
          _eq: X-Hasura-User-Id  # UUID v7 from JWT claims
      limit: 100
      allow_aggregations: false
insert_permissions:
  - role: user
    permission:
      columns: [customer_id, total]  # id excluded — set by DEFAULT
      check:
        customer_id:
          _eq: X-Hasura-User-Id

Extracting timestamps in GraphQL responses

query OrderWithTimestamp($id: uuid!) {
  orders_by_pk(id: $id) {
    id
    total
    status
    # No created_at column — extract from UUID v7 id in the client
  }
}
// Client-side: extract creation time from UUID v7 id
function extractCreatedAt(uuidV7: string): Date {
  const hex = uuidV7.replace(/-/g, '').slice(0, 12);
  return new Date(parseInt(hex, 16));
}

// Usage
const order = data.orders_by_pk;
const createdAt = extractCreatedAt(order.id);

See UUID Bit Fields for the 48-bit timestamp layout.

Hasura event triggers with UUID v7 correlation

# hasura/metadata/databases/default/event_triggers/order_created.yaml
name: order_created
table:
  schema: public
  name: orders
webhook: '{{WEBHOOK_URL}}/order-created'
insert:
  columns: '*'
// Webhook handler — correlate with UUID v7 order ID
app.post('/order-created', (req, res) => {
  const { event } = req.body;
  const orderId = event.data.new.id; // UUID v7
  // orderId encodes creation time — no timestamp parsing needed
  console.log(`Order ${orderId} created`);
  res.json({ received: true });
});

Further reading

External references

Frequently asked questions

How do I set UUID v7 as a default in Hasura's PostgreSQL database?

On PostgreSQL 18 use DEFAULT gen_random_uuid_v7() as the column default. On PostgreSQL 15–17 install the pg_uuidv7 extension and use DEFAULT uuid_generate_v7(). Hasura reads the column default from PostgreSQL and omits the field from the generated GraphQL insert mutation input type, so clients never pass IDs explicitly. See PostgreSQL 18 Native UUID v7.

How do I sort Hasura queries chronologically using UUID v7?

Use order_by: {id: asc} in your Hasura GraphQL query. UUID v7's 48-bit timestamp prefix means lexicographic ascending order equals insertion order. This eliminates the need for a created_at sort column. For cursor-based pagination use Hasura's built-in where: {id: {_gt: $cursor}} filter.

Can I use UUID v7 in Hasura permission rules?

Yes. In Hasura's row-level permission expressions, compare UUID v7 values with _eq, _gt, or _lt. A common pattern: restrict reads to {user_id: {_eq: "X-Hasura-User-Id"}} where X-Hasura-User-Id is a UUID v7 set in the JWT claims. UUID v7 comparison works correctly in Hasura's permission engine because PostgreSQL's native UUID type supports all comparison operators.