pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #3571: chore(deps): update dependency sbt/sbt to v1.10.11
2025-03-24 06:28 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3570: chore(deps): update dependency com.typesafe.play:sbt-plugin to v2.9.7
2025-03-24 02:42 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3569: chore(deps): update codecov/codecov-action digest to 3440e5e
2025-03-24 02:42 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-01-31 09:14 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-01-31 13:23 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-03 04:38 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-04 15:58 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-04 16:52 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-04 17:47 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-05 03:55 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-05 10:43 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-05 17:54 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-10 16:11 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-10 16:21 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-10 17:16 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-10 19:39 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-11 04:30 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-11 10:08 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-02-17 06:39 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-18 16:04 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-19 11:24 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-19 15:01 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-19 16:02 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-20 10:13 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-20 13:22 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-20 13:25 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-20 13:42 UTC "avinashyn (@avinashyn)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3504: Wrong schemas fetched for a given catalog as input
2025-03-20 14:29 UTC "vlsi (@vlsi)" <[email protected]>
[25+ messages in thread]
[pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 01:55 UTC "tordmjohnson (@tordmjohnson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 09:51 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 10:07 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 10:47 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 10:53 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 11:10 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 11:15 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 11:17 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 11:20 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 14:45 UTC "tordmjohnson (@tordmjohnson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 16:35 UTC "jorsol (@jorsol)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 18:43 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-09-11 20:20 UTC "jorsol (@jorsol)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-10-20 10:44 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-10-20 13:49 UTC "tordmjohnson (@tordmjohnson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-10-20 15:20 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-10-20 15:22 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2017-10-22 01:46 UTC "tordmjohnson (@tordmjohnson)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2021-10-08 08:17 UTC "marcmuel (@marcmuel)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2021-10-08 08:31 UTC "marcmuel (@marcmuel)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2021-10-08 09:10 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-18 19:08 UTC "matthias-mueller (@matthias-mueller)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-18 22:38 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-19 06:54 UTC "matthias-mueller (@matthias-mueller)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-19 09:42 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-19 09:55 UTC "matthias-mueller (@matthias-mueller)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-19 12:13 UTC "sehrope (@sehrope)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-20 07:03 UTC "matthias-mueller (@matthias-mueller)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
2025-03-20 10:30 UTC "davecramer (@davecramer)" <[email protected]>
[29+ messages in thread]
[pgjdbc/pgjdbc] PR #3566: Fix JavadocTagContinuationIndentation in AfterBeforeParameterResolver
2025-03-15 17:24 UTC "Anmol202005 (@Anmol202005)" <[email protected]>
[pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-09 14:44 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-09 21:28 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 17:05 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 18:57 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 19:01 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 19:02 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 19:06 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-12 20:20 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-13 07:26 UTC "rtrier (@rtrier)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3562: After insert with PreparedStatement into table with complex types querying leads to resultset with incorrect type
2025-03-13 15:29 UTC "davecramer (@davecramer)" <[email protected]>
[10+ messages in thread]
[pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-02-20 11:45 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-02-20 12:01 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-02-28 10:09 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-02-28 12:17 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-07 17:50 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-08 11:38 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-10 10:19 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-10 13:44 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-10 14:37 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-10 14:41 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3533: refactor: Use key_column_usage instead of indnkeyatts in PgDatabaseMetaData for faster speed and improved compatibility
2025-03-12 09:18 UTC "hlcianfagna (@hlcianfagna)" <[email protected]>
[11+ messages in thread]
[pgjdbc/pgjdbc] issue #3563: CallableStatement.getObject(parameterIndex, toClass) does not works
2025-03-10 15:43 UTC "DmitriyGod (@DmitriyGod)" <[email protected]>
[pgjdbc/pgjdbc] PR #3561: remove forcing uppercase and use the function upperCaseFieldLabels instead
2025-03-08 11:36 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3561: remove forcing uppercase and use the function upperCaseFieldLabels instead
2025-03-09 08:33 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3561: remove forcing uppercase and use the function upperCaseFieldLabels instead
2025-03-09 10:40 UTC "davecramer (@davecramer)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3561: remove forcing uppercase and use the function upperCaseFieldLabels instead
2025-03-09 10:56 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] PR #3561: remove forcing uppercase and use the function upperCaseFieldLabels instead
2025-03-09 10:59 UTC "davecramer (@davecramer)" <[email protected]>
[5+ messages in thread]
[pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-03 11:07 UTC "MaxMello (@MaxMello)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-03 11:12 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-03 13:43 UTC "MaxMello (@MaxMello)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-03 15:22 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-03 15:46 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3543: Table meta data is broken if catalog name not equal database name
2025-03-08 11:05 UTC "davecramer (@davecramer)" <[email protected]>
[6+ messages in thread]
[pgjdbc/pgjdbc] issue #3560: Regression in 42.7.5: Liquibase fails on second application start with uppercase database name
2025-03-06 10:40 UTC "jeme95 (@jeme95)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3560: Regression in 42.7.5: Liquibase fails on second application start with uppercase database name
2025-03-06 11:07 UTC "davecramer (@davecramer)" <[email protected]>
[2+ messages in thread]
[pgjdbc/pgjdbc] issue #3559: looks like dead code to me
2025-03-06 09:05 UTC "davecramer (@davecramer)" <[email protected]>
[pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-07 09:39 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-10 07:43 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-12 04:22 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-20 20:42 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-23 19:45 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-24 05:57 UTC "vlsi (@vlsi)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-02-24 06:00 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
` Re: [pgjdbc/pgjdbc] issue #3514: Add PGConnection#getHost, PGConnection#getPort so clients could identify the current host for each connection
2025-03-05 13:36 UTC "robert-mirzakhanian (@robert-mirzakhanian)" <[email protected]>
[8+ messages in thread]
[pgjdbc/pgjdbc] issue #3558: Add SQLState to PSQLException default message
2025-03-05 13:28 UTC "rmagnin-efluid (@rmagnin-efluid)" <[email protected]>
[pgjdbc/pgjdbc] PR #3557: fix(deps): update junit5 monorepo to v5.12.1 - autoclosed
2025-03-04 14:58 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3556: fix(deps): update dependency spotbugs to v4.9.2
2025-03-04 14:58 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3555: fix(deps): update dependency checkstyle to v10.21.4
2025-03-04 14:58 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3554: chore(deps): update dependency sbt/sbt to v1.10.10
2025-03-04 14:58 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3553: fix(deps): update dependency org.openrewrite.rewrite:org.openrewrite.rewrite.gradle.plugin to v7
2025-03-04 13:45 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3552: fix(deps): update dependency org.hamcrest:hamcrest to v3
2025-03-04 07:07 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3551: fix(deps): update dependency net.ltgt.errorprone:net.ltgt.errorprone.gradle.plugin to v4
2025-03-04 07:07 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3550: chore(deps): update dependency ubuntu to v24
2025-03-04 07:07 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3549: fix(deps): update dependency org.ops4j.pax.exam:pax-exam-container-native to v4.14.0 - autoclosed
2025-03-03 23:36 UTC "renovate-bot (@renovate-bot)" <[email protected]>
[pgjdbc/pgjdbc] PR #3548: chore(deps): update dependency sbt/sbt to v1.10.9
2025-03-03 23:36 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