From d866f0374ca688937b905fbebfcc2c5f8dc88b54 Mon Sep 17 00:00:00 2001 From: David Rowley Date: Tue, 11 Apr 2023 18:52:17 +1200 Subject: Doc: use "an SQL" consistently rather than "a SQL" Similarly to what was done in 04539e73f and 7bdd489d3, we standardized on SQL being pronounced "es-que-ell" rather than "sequel" in our documentation. This fixes the instances of "a SQL" that have crept in during the v16 cycle. Discussion: https://postgr.es/m/CAApHDvpML27UqFXnrYO1MJddsKVMQoiZisPvsAGhKE_tsKXquw%40mail.gmail.com --- doc/src/sgml/ecpg.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index a76cf3538f..f52165165d 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -1506,7 +1506,7 @@ EXEC SQL TYPE serial_t IS long; - Any word you declare as a typedef cannot be used as a SQL keyword + Any word you declare as a typedef cannot be used as an SQL keyword in EXEC SQL commands later in the same program. For example, this won't work: @@ -1518,7 +1518,7 @@ EXEC SQL START TRANSACTION; ECPG will report a syntax error for START TRANSACTION, because it no longer - recognizes START as a SQL keyword, + recognizes START as an SQL keyword, only as a typedef. (If you have such a conflict, and renaming the typedef seems impractical, you could write the SQL command @@ -1530,7 +1530,7 @@ EXEC SQL START TRANSACTION; In PostgreSQL releases before v16, use of SQL keywords as typedef names was likely to result in syntax errors associated with use of the typedef itself, rather than use - of the name as a SQL keyword. The new behavior is less likely to + of the name as an SQL keyword. The new behavior is less likely to cause problems when an existing ECPG application is recompiled in a new PostgreSQL release with new keywords. -- cgit v1.2.1