dblink_build_sql_insert -- builds an insert statement using a local
tuple, replacing the selection key field
- values with alternate supplied values
+ values with alternative supplied values
dblink_build_sql_delete -- builds a delete statement using supplied
values for selection key field values
dblink_build_sql_update -- builds an update statement using a local
tuple, replacing the selection key field
- values with alternate supplied values
+ values with alternative supplied values
Synopsis
Their order was lost,
as was the number of times each lexeme appeared.
You must keep in mind that directly creating vectors with casting
-is <i>not</i> an alternate means of parsing;
+is <i>not</i> an alternative means of parsing;
it is a way of directly entering lexemes into a vector <i>without</i> parsing.
<p>
Queries can also be created through casting,
general, to escape an octet, it is converted into the three-digit
octal number equivalent of its decimal octet value, and preceded
by two backslashes. <xref linkend="datatype-binary-sqlesc">
- shows the characters that must be escaped, and gives the alternate
+ shows the characters that must be escaped, and gives the alternative
escape sequences where applicable.
</para>
<literal>%Ow</literal>
<literal>%OW</literal>
<literal>%Oy</literal>
- are supposed to provide alternate representations.
+ are supposed to provide alternative representations.
</para>
<para>
Additionally <literal>%OB</literal> implemented to represent
privileges, but are not users in the usual sense of the word.
If not specified,
<literal>NOLOGIN</literal> is the default, except when
- <command>CREATE ROLE</> is invoked through its alternate spelling
+ <command>CREATE ROLE</> is invoked through its alternative spelling
<command>CREATE USER</>.
</para>
</listitem>
<para>
The <productname>PostgreSQL</productname> rule system allows one to
- define an alternate action to be performed on insertions, updates,
+ define an alternative action to be performed on insertions, updates,
or deletions in database tables. Roughly speaking, a rule causes
additional commands to be executed when a given command on a given
table is executed. Alternatively, an <literal>INSTEAD</literal>
*
* This caches attribute offsets in the attribute descriptor.
*
- * An alternate way to speed things up would be to cache offsets
+ * An alternative way to speed things up would be to cache offsets
* with the tuple, but that seems more difficult unless you take
* the storage hit of actually putting those offsets into the
* tuple you send to disk. Yuck.
*
* This caches attribute offsets in the attribute descriptor.
*
- * An alternate way to speed things up would be to cache offsets
+ * An alternative way to speed things up would be to cache offsets
* with the tuple, but that seems more difficult unless you take
* the storage hit of actually putting those offsets into the
* tuple you send to disk. Yuck.
/* ----------------
* heap_beginscan - begin relation scan
*
- * heap_beginscan_bm is an alternate entry point for setting up a HeapScanDesc
+ * heap_beginscan_bm is an alternative entry point for setting up a HeapScanDesc
* for a bitmap heap scan. Although that scan technology is really quite
* unlike a standard seqscan, there is just enough commonality to make it
* worth using the same data structure.
/*
* If a commutator and/or negator link is provided, update the other
* operator(s) to point at this one, if they don't already have a link.
- * This supports an alternate style of operator definition wherein the
+ * This supports an alternative style of operator definition wherein the
* user first defines one operator without giving negator or commutator,
* then defines the other operator of the pair with the proper commutator
* or negator attribute. That style doesn't require creation of a shell,
/usr/bin/ssh -1 -i $IDENTITY -n $HOST 'sleep 60' & \
/usr/bin/psql -h $HOST -p 5555 $1
-Alternately, the system could run a daemon that establishes and maintains
+Alternatively, the system could run a daemon that establishes and maintains
the tunnel. This is preferrable when multiple users need to establish
similar tunnels to the same remote site.
* unsecured connection without fully informing the user.
* Very uncool.
*
- * Alternately, the backend could attempt to load these files
+ * Alternatively, the backend could attempt to load these files
* on startup if SSL is enabled - and refuse to start if any
* do not exist - but this would tend to piss off DBAs.
*
* schemavar: name of query variable to match against a schema-name pattern.
* Can be NULL if no schema.
* namevar: name of query variable to match against an object-name pattern.
- * altnamevar: NULL, or name of an alternate variable to match against name.
+ * altnamevar: NULL, or name of an alternative variable to match against name.
* visibilityrule: clause to use if we want to restrict to visible objects
* (for example, "pg_catalog.pg_table_is_visible(p.oid)"). Can be NULL.
*
StartBlobPtr StartBlobPtr;
EndBlobPtr EndBlobPtr;
- CustomOutPtr CustomOutPtr; /* Alternate script output routine */
+ CustomOutPtr CustomOutPtr; /* Alternative script output routine */
/* Stuff for direct DB connection */
char *archdbname; /* DB name *read* from archive */
printf(_("\nConnection options:\n"));
printf(_(" -h, --host=HOSTNAME database server host or socket directory\n"));
- printf(_(" -l, --database=dbname specify an alternate default database\n"));
+ printf(_(" -l, --database=dbname specify an alternative default database\n"));
printf(_(" -p, --port=PORT database server port number\n"));
printf(_(" -U, --username=NAME connect as specified database user\n"));
printf(_(" -W, --password force password prompt (should happen automatically)\n"));
/*
- * MinimalTuple is an alternate representation that is used for transient
+ * MinimalTuple is an alternative representation that is used for transient
* tuples inside the executor, in places where transaction status information
* is not required, the tuple rowtype is known, and shaving off a few bytes
* is worthwhile because we need to store many tuples. The representation
* String definitions for standard time quantities.
*
* These strings are the defaults used to form output time strings.
- * Other alternate forms are hardcoded into token tables in datetime.c.
+ * Other alternative forms are hardcoded into token tables in datetime.c.
* ----------------------------------------------------------------
*/
/*
- * Alternate handler for unsafe functions
+ * Alternative handler for unsafe functions
*/
PG_FUNCTION_INFO_V1(pltclu_call_handler);
ERROR: time zone displacement out of range: "Feb 16 17:32:01 -0097"
INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC');
ERROR: timestamp out of range: "Feb 16 17:32:01 5097 BC"
--- Alternate field order that we've historically supported (sort of)
+-- Alternative field order that we've historically supported (sort of)
-- with regular and POSIXy timezone specs
SELECT 'Wed Jul 11 10:51:14 America/New_York 2001'::timestamptz;
timestamptz
INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 -0097');
INSERT INTO TIMESTAMPTZ_TBL VALUES ('Feb 16 17:32:01 5097 BC');
--- Alternate field order that we've historically supported (sort of)
+-- Alternative field order that we've historically supported (sort of)
-- with regular and POSIXy timezone specs
SELECT 'Wed Jul 11 10:51:14 America/New_York 2001'::timestamptz;
SELECT 'Wed Jul 11 10:51:14 GMT-4 2001'::timestamptz;
projects / users / bernd / postgres.git / commitdiff