/rtmp/upsert.diff
text/x-diff
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: unified
| File | + | − |
|---|---|---|
| doc/src/sgml/plpgsql.sgml | 0 | 0 |
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index c342916..d2e74dc 100644
*** a/doc/src/sgml/plpgsql.sgml
--- b/doc/src/sgml/plpgsql.sgml
*************** BEGIN
*** 2464,2470 ****
INSERT INTO db(a,b) VALUES (key, data);
RETURN;
EXCEPTION WHEN unique_violation THEN
! -- do nothing, and loop to try the UPDATE again
END;
END LOOP;
END;
--- 2464,2470 ----
INSERT INTO db(a,b) VALUES (key, data);
RETURN;
EXCEPTION WHEN unique_violation THEN
! -- Do nothing, and loop to try the UPDATE again.
END;
END LOOP;
END;
*************** LANGUAGE plpgsql;
*** 2474,2480 ****
SELECT merge_db(1, 'david');
SELECT merge_db(1, 'dennis');
</programlisting>
!
</para>
</example>
</sect2>
--- 2474,2483 ----
SELECT merge_db(1, 'david');
SELECT merge_db(1, 'dennis');
</programlisting>
! This example assumes the <literal>unique_violation</> error is caused by
! the <command>INSERT</>, and not by an <command>INSERT</> trigger function
! on the table. Also, this example only works in the default Read
! Committed transaction mode.
</para>
</example>
</sect2>