Skip to content

Commit

Permalink
doc: fix spelling mistakes (#868)
Browse files Browse the repository at this point in the history
  • Loading branch information
davecramer authored and vlsi committed Jul 31, 2017
1 parent 5c12da1 commit 757db62
Show file tree
Hide file tree
Showing 5 changed files with 9 additions and 11 deletions.
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -89,7 +89,7 @@ Notable changes for:
* fix: infinite dates might be corrupted when transferred in binary for certain JREs. For instance, 5881610-07-11 instead of infinity.

**[42.1.0]** (2017-05-04):
* fix: data being trucated in setCharacterStream (the bug introduced in 42.0.0) [PR#802](https://github.com/pgjdbc/pgjdbc/pull/802)
* fix: data being truncated in setCharacterStream (the bug introduced in 42.0.0) [PR#802](https://github.com/pgjdbc/pgjdbc/pull/802)
* fix: calculation of lastReceiveLSN for logical replication [PR#801](https://github.com/pgjdbc/pgjdbc/pull/801)
* fix: make sure org.postgresql.Driver is loaded when accessing though DataSource interface [#768](https://github.com/pgjdbc/pgjdbc/issues/768)
* feat: support fetching a REF_CURSOR using getObject [PR#809](https://github.com/pgjdbc/pgjdbc/pull/809)
Expand Down
2 changes: 1 addition & 1 deletion docs/_posts/2017-05-04-42.1.0-release.md
Expand Up @@ -69,7 +69,7 @@ Vladimir Sitnikov (3):

slmsbrhgn (1):

* bug: fix data being trucated in setCharacterStream (the bug introduced in 42.0.0) [PR#802](https://github.com/pgjdbc/pgjdbc/pull/802) [28c98418](https://github.com/pgjdbc/pgjdbc/commit/28c98418b576394b7a0a4a6415ae86ba47be40ae)
* bug: fix data being truncated in setCharacterStream (the bug introduced in 42.0.0) [PR#802](https://github.com/pgjdbc/pgjdbc/pull/802) [28c98418](https://github.com/pgjdbc/pgjdbc/commit/28c98418b576394b7a0a4a6415ae86ba47be40ae)

<a name="contributors_{{ page.version }}"></a>
### Contributors to this release
Expand Down
4 changes: 2 additions & 2 deletions docs/documentation/head/escaped-functions.md
Expand Up @@ -15,7 +15,7 @@ The driver supports the nesting and the mixing of escaped functions and escaped
values. The appendix C of the JDBC specification describes the functions.

Some functions in the following tables are translated but not reported as supported
because they are duplicating or changing ther order of the arguments. While this
because they are duplicating or changing their order of the arguments. While this
is harmless for literal values or columns, it will cause problems when using
prepared statements. For example "`{fn right(?,?)}`" will be translated to "`substring(? from (length(?)+1-?))`".
As you can see the translated SQL requires more parameters than before the
Expand Down Expand Up @@ -477,4 +477,4 @@ or SQL_TSI_FRAC_DAY is supported </td>
<td>&nbsp;</td>
</tr>
</tbody>
</table>
</table>
8 changes: 3 additions & 5 deletions docs/documentation/head/escapes.md
Expand Up @@ -21,10 +21,8 @@ some vendor specific SQL may be required for certain RDBMS features. To aid
developers in writing portable JDBC applications across multiple database products,
a special escape syntax is used to specify the generic commands the developer
wants to be run. The JDBC driver translates these escape sequences into native
syntax for its specific database. For more information consult the section 4.1.5
from the [JDBC Technology Guide](http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/statement.html#999472)
(bundled with the Oracle™ JRE documentation) and the section 13.4 from the
[JDBC 3.0 specification](http://java.sun.com/products/jdbc/download.html#corespec30).
syntax for its specific database. For more information consult the
[Java DB Technical Documentation](http://docs.oracle.com/javadb/10.10.1.2/ref/rrefjdbc1020262.html).

The parsing of the sql statements for these escapes can be disabled using
`Statement.setEscapeProcessing(false)`.
Expand All @@ -33,7 +31,7 @@ The parsing of the sql statements for these escapes can be disabled using
It translates the given SQL to a SQL suitable for the PostgreSQL™ backend.

<a name="escape-use-example"></a>
**Example 8.1. Using jdbc escapes**
**Example 8.1. Using JDBC escapes**

To use the JDBC escapes, you simply write your SQL replacing date/time literal
values, outer join and functions by the JDBC escape syntax. For example :
Expand Down
4 changes: 2 additions & 2 deletions docs/documentation/head/listennotify.md
Expand Up @@ -24,7 +24,7 @@ any outstanding notifications.

> A key limitation of the JDBC driver is that it cannot receive asynchronous
notifications and must poll the backend to check if any notifications were issued.
I timeout can be given to the poll function, but then the execution of statements
A timeout can be given to the poll function, but then the execution of statements
from other threads will block.

<a name="listen-notify-example"></a>
Expand Down Expand Up @@ -86,7 +86,7 @@ class Listener extends Thread

if (notifications != null)
{
for (int i=0; i&lt;notifications.length; i++)
for (int i=0; i < notifications.length; i++)
System.out.println("Got notification: " + notifications[i].getName());
}

Expand Down

0 comments on commit 757db62

Please sign in to comment.