pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  
help / color / mirror / Atom feed
[pgjdbc/pgjdbc] PR #3613: Deprecate group startup parms
  2025-04-29 18:49 UTC  "davecramer (@davecramer)" <[email protected]>

[pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-16 06:32 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-17 07:52 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-17 10:31 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-17 11:28 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-17 12:24 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-17 18:04 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-28 13:15 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-28 13:32 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-28 14:56 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-29 07:11 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3607: Copr: Use Java 21 as the build dependency
  2025-04-29 11:19 UTC  "vlsi (@vlsi)" <[email protected]>
  [11+ messages in thread]

[pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 22:47 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 22:51 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 22:59 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 23:02 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 23:09 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 23:24 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 23:41 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-04 23:44 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:12 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:14 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:15 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:17 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:23 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:24 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:25 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:25 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:31 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:42 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:46 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 00:54 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 01:00 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 01:01 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 03:29 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-05 10:44 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-06 22:32 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-18 22:27 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-19 15:20 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-19 16:21 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-19 23:32 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-02-28 19:55 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-03-17 15:36 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-04-02 16:15 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-04-15 17:45 UTC  "joejensen (@joejensen)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3509: Add back application name setting
  2025-04-28 22:37 UTC  "davecramer (@davecramer)" <[email protected]>
  [34+ messages in thread]

[pgjdbc/pgjdbc] PR #3611: fix indentation of return child to allow built pass in Checkstyle's CIs
  2025-04-28 08:19 UTC  "mohitsatr (@mohitsatr)" <[email protected]>

[pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-16 06:22 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-18 16:48 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-18 18:33 UTC  "jankohlmann (@jankohlmann)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-18 18:45 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 05:57 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 06:39 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 10:04 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 10:21 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 10:32 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 11:58 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 12:05 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 12:45 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-19 12:46 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-20 12:00 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-21 08:18 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-21 08:19 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-21 10:53 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-21 12:51 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-02-27 15:49 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-23 11:06 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-23 19:35 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-23 19:35 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 10:58 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 11:45 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 12:18 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 13:00 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 15:54 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-24 17:25 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-25 11:52 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-25 13:37 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3526: Set column name explicitely when using `current_database()` in queries
  2025-04-25 13:39 UTC  "davecramer (@davecramer)" <[email protected]>
  [31+ messages in thread]

[pgjdbc/pgjdbc] issue #3527: Improve compatibility with non-Postgres databases
  2025-02-18 16:10 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3527: Improve compatibility with non-Postgres databases
  2025-02-24 07:28 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3527: Improve compatibility with non-Postgres databases
  2025-02-24 09:17 UTC  "kneth (@kneth)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3527: Improve compatibility with non-Postgres databases
  2025-04-25 13:38 UTC  "kneth (@kneth)" <[email protected]>
  [4+ messages in thread]

[pgjdbc/pgjdbc] issue #3610: postgresql-42.7.5.jar against a server 17.4 throws an error
  2025-04-23 08:56 UTC  "bdnced (@bdnced)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3610: postgresql-42.7.5.jar against a server 17.4 throws an error
  2025-04-23 09:48 UTC  "davecramer (@davecramer)" <[email protected]>
  [2+ messages in thread]

[pgjdbc/pgjdbc] PR #3609: add PgMessageType and use static variables for protocol literals
  2025-04-22 22:36 UTC  "davecramer (@davecramer)" <[email protected]>

[pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-05 19:40 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-05 21:39 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-06 12:30 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-06 20:04 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-09 18:00 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-09 18:02 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-09 18:02 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-09 18:04 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-09 18:05 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-10 09:38 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-10 09:55 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-10 10:11 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-10 20:21 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-12 13:13 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-13 08:19 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-13 08:21 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-13 08:24 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-18 21:34 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-18 21:37 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3589: Metadata CHAR_OCTET_LENGTH is a positive number for non-character column types
  2025-04-18 21:53 UTC  "tirthgajera (@tirthgajera)" <[email protected]>
  [20+ messages in thread]

[pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 08:54 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 10:52 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 11:41 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 11:56 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 12:06 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 12:13 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-26 12:21 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-27 14:40 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-28 18:34 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-28 18:48 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-28 19:00 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 08:53 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 11:01 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 11:16 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 12:39 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 12:49 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-08-29 13:05 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2024-11-18 19:13 UTC  "kimjand (@kimjand)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-15 10:38 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-22 17:05 UTC  "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-22 18:38 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-22 19:27 UTC  "ecki (@ecki)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-22 21:21 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-22 21:28 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-01-27 08:07 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-02-26 14:32 UTC  "miroslav-vacek (@miroslav-vacek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-02-26 14:38 UTC  "jcharaoui (@jcharaoui)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-02-26 14:40 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-03-20 06:50 UTC  "PenghaiZhang (@PenghaiZhang)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-04-01 17:51 UTC  "rbrw (@rbrw)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-04-10 09:01 UTC  "df7cb (@df7cb)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-04-10 09:15 UTC  "MrEasy (@MrEasy)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-04-17 11:32 UTC  "df7cb (@df7cb)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
  2025-04-18 21:34 UTC  "danielvion (@danielvion)" <[email protected]>
  [34+ messages in thread]

[pgjdbc/pgjdbc] issue #3608: Support BigInteger[] in PgPreparedStatement#setObject(int, java.lang.Object)
  2025-04-17 15:50 UTC  "victornoel (@victornoel)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3608: Support BigInteger[] in PgPreparedStatement#setObject(int, java.lang.Object)
  2025-04-17 16:12 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3608: Support BigInteger[] in PgPreparedStatement#setObject(int, java.lang.Object)
  2025-04-17 16:45 UTC  "victornoel (@victornoel)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3608: Support BigInteger[] in PgPreparedStatement#setObject(int, java.lang.Object)
  2025-04-17 16:53 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3608: Support BigInteger[] in PgPreparedStatement#setObject(int, java.lang.Object)
  2025-04-18 07:11 UTC  "victornoel (@victornoel)" <[email protected]>
  [5+ messages in thread]

[pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-11 19:40 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 07:09 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 07:17 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 07:28 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 07:29 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 07:39 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 08:02 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 08:04 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 08:06 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-13 08:10 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-14 19:31 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-15 18:26 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-15 18:27 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-15 18:29 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-15 18:29 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 01:45 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 11:41 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 11:48 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 11:52 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 11:57 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:00 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:02 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:02 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:04 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:04 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 12:07 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 13:17 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 13:17 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 13:18 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 13:19 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 13:34 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 15:06 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 15:09 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 15:11 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 15:12 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-16 15:14 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3592:  Handle protocol 3.2 and wider cancel keys. 
  2025-04-17 12:34 UTC  "davecramer (@davecramer)" <[email protected]>
  [37+ messages in thread]

[pgjdbc/pgjdbc] issue #3605: PgConnection.setSchema() does not support multiple schemas
  2025-04-15 07:36 UTC  "cgm-aw (@cgm-aw)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3605: PgConnection.setSchema() does not support multiple schemas
  2025-04-15 12:31 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3605: PgConnection.setSchema() does not support multiple schemas
  2025-04-15 14:31 UTC  "cgm-aw (@cgm-aw)" <[email protected]>
  [3+ messages in thread]

[pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-11 09:51 UTC  "praiskup (@praiskup)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-11 10:01 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-11 10:05 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-11 10:08 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-15 13:37 UTC  "praiskup (@praiskup)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-15 13:55 UTC  "mkoncek (@mkoncek)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3591: The Fedora CI seems to fail
  2025-04-15 14:10 UTC  "praiskup (@praiskup)" <[email protected]>
  [7+ messages in thread]

[pgjdbc/pgjdbc] PR #3604: fix(deps): update dependency org.ops4j.pax.exam:pax-exam-junit4 to v4.14.0 - autoclosed
  2025-04-14 23:52 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3603: chore(deps): update codecov/codecov-action digest to ad3126e
  2025-04-14 23:51 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3602: fix(deps): update dependency org.openrewrite.rewrite:org.openrewrite.rewrite.gradle.plugin to v7.4.1
  2025-04-14 18:07 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3601: fix(deps): update dependency checkstyle to v10.23.0 - autoclosed
  2025-04-14 18:07 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-02-18 20:47 UTC  "SophiahHo (@SophiahHo)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-02-19 00:43 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-02-19 14:21 UTC  "SophiahHo (@SophiahHo)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-02-19 15:22 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-02 14:51 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-03 14:27 UTC  "SophiahHo (@SophiahHo)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-09 18:39 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-09 19:03 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-13 08:42 UTC  "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-13 10:51 UTC  "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3528: Implement performance fix for catalog check in DatabaseMetaData
  2025-04-14 14:46 UTC  "davecramer (@davecramer)" <[email protected]>
  [11+ messages in thread]

[pgjdbc/pgjdbc] PR #3600: fix(deps): update dependency de.thetaphi.forbiddenapis:de.thetaphi.forbiddenapis.gradle.plugin to v3.9
  2025-04-14 14:46 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3599: fix(deps): update dependency checkstyle to v10.23.0
  2025-04-14 14:46 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3598: chore(deps): update plugin com.github.burrunan.s3-build-cache to v1.9.0
  2025-04-14 11:31 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3597: fix(deps): update dependency org.junit:junit-bom to v5.12.2
  2025-04-14 11:31 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3596: fix(deps): update dependency net.bytebuddy:byte-buddy-parent to v1.17.5
  2025-04-14 05:29 UTC  "renovate-bot (@renovate-bot)" <[email protected]>

[pgjdbc/pgjdbc] PR #3595: fix(deps): update dependency jacoco to v0.8.13
  2025-04-14 05:28 UTC  "renovate-bot (@renovate-bot)" <[email protected]>


[next (older)]

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox