Skip to content

Commit

Permalink
Fixed typos in all source code and documentations (#3242)
Browse files Browse the repository at this point in the history
  • Loading branch information
SheerazMajeedM committed May 10, 2024
1 parent 5c0dbf0 commit f13363e
Show file tree
Hide file tree
Showing 12 changed files with 16 additions and 16 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Expand Up @@ -809,7 +809,7 @@ thrown to caller to be dealt with so no need to log at this verbosity by pgjdbc
- Add support for PreparedStatement.setCharacterStream(int, Reader). [ee4c4265](https://github.com/pgjdbc/pgjdbc/commit/ee4c4265aebc1c73a1d1fabac5ba259d1fbfd1e4)

### Changed
- Version bumped to 42.0.0 to avoid version clash with PostgreSQL version and follow a better sematic versioning. [46634923](https://github.com/pgjdbc/pgjdbc/commit/466349236622c6b03bb9cd8d7f517c3ce0586751)
- Version bumped to 42.0.0 to avoid version clash with PostgreSQL version and follow a better semantic versioning. [46634923](https://github.com/pgjdbc/pgjdbc/commit/466349236622c6b03bb9cd8d7f517c3ce0586751)
- Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0. [Issue 742](https://github.com/pgjdbc/pgjdbc/issues/742)
- Error position is displayed when SQL has unterminated literals, comments, etc. [Issue 688](https://github.com/pgjdbc/pgjdbc/issues/688)
- Strict handling of accepted values in getBoolean and setObject(BOOLEAN), now it follows PostgreSQL accepted values, only 1 and 0 for numeric types are accepted (previously !=0 was true). [PR 732](https://github.com/pgjdbc/pgjdbc/pull/732)
Expand Down
2 changes: 1 addition & 1 deletion TESTING.md
Expand Up @@ -108,7 +108,7 @@ You could specify Java version for testing purposes with `-PjdkTestVersion=8` bu
./gradlew -PjdkTestVersion=8 test
```

You could lauch `./gradlew parameters` to get the list of available parameters.
You could launch `./gradlew parameters` to get the list of available parameters.

If the test suite reports errors or failures that you cannot
explain, please post the relevant parts of the output to the
Expand Down
2 changes: 1 addition & 1 deletion docs/content/changelogs/2017-02-20-42.0.0-release.md
Expand Up @@ -15,7 +15,7 @@ version: 42.0.0
* Version bumped to 42.0.0 to avoid version clash with PostgreSQL version and follow a better semantic versioning. [46634923](https://github.com/pgjdbc/pgjdbc/commit/66349236622c6b03bb9cd8d7f517c3ce0586751)
* Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0. [Issue 742](https://github.com/pgjdbc/pgjdbc/issues/742)
* Error position is displayed when SQL has unterminated literals, comments, etc. [Issue 688](https://github.com/pgjdbc/pgjdbc/issues/688)
* Strict handling of accepted values in getBoolean and setObject(BOOLEAN), now it follows PostgreSQL accepted values, only 1 and 0 for numeric types are acepted (previusly !=0 was true). [PR 732](https://github.com/pgjdbc/pgjdbc/pull/732)
* Strict handling of accepted values in getBoolean and setObject(BOOLEAN), now it follows PostgreSQL accepted values, only 1 and 0 for numeric types are accepted (previously !=0 was true). [PR 732](https://github.com/pgjdbc/pgjdbc/pull/732)
* Return correct versions and name of the driver. [PR 668](https://github.com/pgjdbc/pgjdbc/pull/668)

#### Removed
Expand Down
4 changes: 2 additions & 2 deletions docs/content/changelogs/2023-03-17-42.6.0-release.md
Expand Up @@ -9,7 +9,7 @@ version: 42.6.0


### Fixed
* fix: use `PhantomReferences` instead of `Obejct.finalize()` to track Connection leaks [PR #2847](https://github.com/pgjdbc/pgjdbc/pull/2847)\
* fix: use `PhantomReferences` instead of `Object.finalize()` to track Connection leaks [PR #2847](https://github.com/pgjdbc/pgjdbc/pull/2847)\
The change replaces all uses of Object.finalize() with PhantomReferences.
The leaked resources (Connections) are tracked in a helper thread that is active as long as
there are connections in use. By default, the thread keeps running for 30 seconds after all
Expand All @@ -28,4 +28,4 @@ Rob Bygrave (1):
* refactor:(loom) replace the usages of synchronized with ReentrantLock [PR #2635](https://github.com/pgjdbc/pgjdbc/pull/2635)

Vladimir Sitnikov (1):
* fix: use `PhantomReferences` instead of `Obejct.finalize()` to track Connection leaks [PR #2847](https://github.com/pgjdbc/pgjdbc/pull/2847)
* fix: use `PhantomReferences` instead of `Object.finalize()` to track Connection leaks [PR #2847](https://github.com/pgjdbc/pgjdbc/pull/2847)
2 changes: 1 addition & 1 deletion docs/content/documentation/server-prepare.md
Expand Up @@ -754,7 +754,7 @@ while (true) {
As mentioned previously, replication stream should periodically send feedback to the database to prevent disconnect via
timeout. Feedback is automatically sent when `read` or `readPending` are called if it's time to send feedback. Feedback
can also be sent via `org.postgresql.replication.PGReplicationStream#forceUpdateStatus()` regardless of the timeout. Another
important duty of feedback is to provide the server with the Logial Sequence Number (LSN) that has been successfully received
important duty of feedback is to provide the server with the Logical Sequence Number (LSN) that has been successfully received
and applied to consumer, it is necessary for monitoring and to truncate/archive WAL's that that are no longer needed. In the
event that replication has been restarted, it's will start from last successfully processed LSN that was sent via feedback to database.

Expand Down
2 changes: 1 addition & 1 deletion docs/static/js/menutoggle.js
@@ -1,4 +1,4 @@
// Grab any element that has the 'js-toggle' class and add an event listner for the toggleClass function
// Grab any element that has the 'js-toggle' class and add an event listener for the toggleClass function
let toggleBtns = document.getElementsByClassName( 'js-toggle' )
for ( let i = 0; i < toggleBtns.length; i++ ) {
toggleBtns[i].addEventListener( 'click', toggleClass, false )
Expand Down
Expand Up @@ -91,7 +91,7 @@ public int peek() throws IOException {
}

/**
* Reads byte from the buffer without any checks. This method never reads from the underlaying
* Reads byte from the buffer without any checks. This method never reads from the underlying
* stream. Before calling this method the {@link #ensureBytes} method must have been called.
*
* @return The next byte from the buffer.
Expand Down Expand Up @@ -302,7 +302,7 @@ public void close() throws IOException {
* Returns direct handle to the used buffer. Use the {@link #ensureBytes} to prefill required
* bytes the buffer and {@link #getIndex} to fetch the current position of the buffer.
*
* @return The underlaying buffer.
* @return The underlying buffer.
*/
public byte[] getBuffer() {
return buffer;
Expand Down
Expand Up @@ -114,7 +114,7 @@ private ISSPIClient createSSPI(PGStream pgStream,
return c.getDeclaredConstructor(PGStream.class, String.class, boolean.class)
.newInstance(pgStream, spnServiceClass, enableNegotiate);
} catch (Exception e) {
// This catched quite a lot exceptions, but until Java 7 there is no ReflectiveOperationException
// This caught quite a lot exceptions, but until Java 7 there is no ReflectiveOperationException
throw new IllegalStateException("Unable to load org.postgresql.sspi.SSPIClient."
+ " Please check that SSPIClient is included in your pgjdbc distribution.", e);
}
Expand Down
4 changes: 2 additions & 2 deletions pgjdbc/src/main/java/org/postgresql/jdbc/TimestampUtils.java
Expand Up @@ -413,7 +413,7 @@ ParsedTimestamp parseDate(byte[]dateBytes) {
* Parse a string and return a timestamp representing its value.
*
* @param cal calendar to be used to parse the input string
* @param s The ISO formated date string to parse.
* @param s The ISO formatted date string to parse.
* @return null if s is null or a timestamp of the parsed string s.
* @throws SQLException if there is a problem parsing s.
* @deprecated use {@link #toTimestamp(Calendar, byte[])}
Expand Down Expand Up @@ -476,7 +476,7 @@ ParsedTimestamp parseDate(byte[]dateBytes) {
/**
* Parse a string and return a LocalTime representing its value.
*
* @param s The ISO formated time string to parse.
* @param s The ISO formatted time string to parse.
* @return null if s is null or a LocalTime of the parsed string s.
* @throws SQLException if there is a problem parsing s.
*/
Expand Down
4 changes: 2 additions & 2 deletions pgjdbc/src/main/java/org/postgresql/util/PGInterval.java
Expand Up @@ -42,7 +42,7 @@ public PGInterval() {
/**
* Initialize a interval with a given interval string representation.
*
* @param value String representated interval (e.g. '3 years 2 mons')
* @param value String represented interval (e.g. '3 years 2 mons')
* @throws SQLException Is thrown if the string representation has an unknown format
* @see PGobject#setValue(String)
*/
Expand Down Expand Up @@ -132,7 +132,7 @@ public PGInterval(int years, int months, int days, int hours, int minutes, doubl
* Sets a interval string represented value to this instance. This method only recognize the
* format, that Postgres returns - not all input formats are supported (e.g. '1 yr 2 m 3 s').
*
* @param value String representated interval (e.g. '3 years 2 mons')
* @param value String represented interval (e.g. '3 years 2 mons')
* @throws SQLException Is thrown if the string representation has an unknown format
*/
@Override
Expand Down
2 changes: 1 addition & 1 deletion pgjdbc/src/main/java/org/postgresql/xa/PGXAConnection.java
Expand Up @@ -200,7 +200,7 @@ public void start(Xid xid, int flags) throws XAException {
XAException.XAER_PROTO);
}

// We can't check precondition 4 easily, so we don't. Duplicate xid will be catched in prepare
// We can't check precondition 4 easily, so we don't. Duplicate xid will be caught in prepare
// phase.

// Check implementation deficiency preconditions
Expand Down
Expand Up @@ -38,7 +38,7 @@ void run(String input) throws PSQLException {
if (!(cause instanceof NumberFormatException)) {
throw e;
}
// NumerFormatException is expected
// NumberFormatException is expected
}
}
}

0 comments on commit f13363e

Please sign in to comment.