use_an_SQL_not_a_SQL.patch

text/plain

Filename: use_an_SQL_not_a_SQL.patch
Type: text/plain
Part: 0
Message: Re: "an SQL" vs. "a SQL"

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/ddl.sgml 1 1
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index 8ff9a520ca..2aa25f62f5 100644
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -5479,7 +5479,7 @@ CREATE FUNCTION get_color_note (rainbow) RETURNS text AS
   </para>
 
   <para>
-   On the other hand, for a SQL-language function or procedure whose body
+   On the other hand, for an SQL-language function or procedure whose body
    is written in SQL-standard style, the body is parsed at function
    definition time and all dependencies recognized by the parser are
    stored.  Thus, if we write the function above as