pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
33+ messages / 5 participants
[nested] [flat]
* [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-09-26 20:29 "SophiahHo (@SophiahHo)" <[email protected]>
0 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-09-26 20:29 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Fixes https://github.com/pgjdbc/pgjdbc/issues/3389 "Metadata results from getSchemas(String catalog, String schemaPattern) violate JDBC spec"
Fixes https://github.com/pgjdbc/pgjdbc/issues/3394 "getSchemas with empty string for schemaPattern returns schemas, violating JDBC spec"
### All Submissions:
* [x] Have you followed the guidelines in our [Contributing](https://github.com/pgjdbc/pgjdbc/blob/master/CONTRIBUTING.md) document?
* [x] Have you checked to ensure there aren't other open [Pull Requests](../../pulls) for the same update/change?
<!-- You can erase any parts of this template not applicable to your Pull Request. -->
### Changes to Existing Features:
* [ ] Does this break existing behaviour? If so please explain.
* [x] Have you added an explanation of what your changes do and why you'd like us to include them?
* [x] Have you written new tests for your core changes, as applicable?
* [x] Have you successfully run tests with your changes locally?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-09-26 21:47 "svendiedrichsen (@svendiedrichsen)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: svendiedrichsen (@svendiedrichsen) @ 2024-09-26 21:47 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java)
Why not ignore this case like the NULL case? And if ignore it like NULL you can simplify the whole if like in the schemaPattern if below.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-09-27 13:01 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-09-27 13:01 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java)
as appealing as it is to use the `information schema`, this is actually a view and adds another select into this query. Is there any reason to do this ?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-09-27 15:03 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-09-27 15:03 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java)
If `catalog` is `""`, then getSchemas should return schemas "without a catalog" per [JDBC spec:](https://docs.oracle.com/en/java/javase/17/docs/api/java.sql/java/sql/DatabaseMetaData.html#getSchema...))
> catalog - a catalog name; must match the catalog name as it is stored in the database;"" retrieves those without a catalog; null means catalog name should not be used to narrow down the search.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-09-27 15:03 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-09-27 15:03 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java)
Fixed
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-10-01 13:24 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-10-01 13:24 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I removed the empty string check for `schemaPattern`, because no rows should be returned if `schemaPattern` is an empty string per JDBC spec.
> schemaPattern - a schema name; must match the schema name as it is stored in the database; null means schema name should not be used to narrow down the search.
Please approve.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-10-03 14:14 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-10-03 14:14 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I have added new tests and updated the existing test.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-10-04 15:05 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-10-04 15:05 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Mapping the catalog name to the database name is already canonical in postgres itself, because when I `select pg_get_viewdef('information_schema.schemata', true);`, postgres returns the following view definition:
```sql
SELECT current_database()::information_schema.sql_identifier AS catalog_name,
n.nspname::information_schema.sql_identifier AS schema_name,
u.rolname::information_schema.sql_identifier AS schema_owner,
NULL::name::information_schema.sql_identifier AS default_character_set_catalog,
NULL::name::information_schema.sql_identifier AS default_character_set_schema,
NULL::name::information_schema.sql_identifier AS default_character_set_name,
NULL::character varying::information_schema.character_data AS sql_path
FROM pg_namespace n,
pg_authid u
WHERE n.nspowner = u.oid AND (pg_has_role(n.nspowner, 'USAGE'::text) OR has_schema_privilege(n.oid, 'CREATE, USAGE'::text));
```
An alternative to using `current_database()::information_schema.sql_identifier` for `TABLE_CATALOG` is to select `catalog_name` from the view `information_schema.schemata` to make the driver future-compatible with any design changes in postgres that would allow a postgres connection to access multiple databases. However, as you had alluded, the disadvantage would be the performance hit from the view selecting from `pg_authid`.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-10-15 13:54 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-10-15 13:54 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@SophiahHo I don't think in the case of PostgreSQL there will ever be a situation where a connection can access another database.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-10-17 15:07 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-10-17 15:07 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer I added a comment on https://github.com/pgjdbc/pgjdbc/issues/3389 to explain that https://github.com/pgjdbc/pgjdbc/commit/9ea59bd87f7920f1c2aba20ffef15acef85def60 added partial support for catalogs and broke things.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-10 14:56 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-10 14:56 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer When our enterprise customers upgraded their pgjdbc driver from a version older than 42.7.0 to a version between 42.7.0 and 42.7.4, they are getting [duplicated database objects for metadata queries.](https://github.com/pgjdbc/pgjdbc/issues/3389#issuecomment-2414487622) As a workaround, we asked our enterprise customers to downgrade their pgjdbc driver to a version before 42.7.0. This MR fixes this bug so that our enterprise users would be able to use the latest pgjdbc driver with security updates.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-10 18:17 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-10 18:17 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java:283)
Searching with an empty catalog and schema is valid. Please add another test instead of just changing this one
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-10 19:45 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-10 19:45 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java:283)
@davecramer Per https://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#getColumns-java.lang.String...- :
> Parameters:
catalog - a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog; null means that the catalog name should not be used to narrow the search
schemaPattern - a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema; null means that the schema name should not be used to narrow the search
Searching with an empty catalog and schema should return no results. If you don't want the change in behaviour for how empty strings are handled, I can remove it, because it's not a priority for me/us. However, the current behaviour technically violates the JDBC spec.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-10 20:53 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-10 20:53 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java:283)
I didn't say I wanted to change the behaviour; I said I wanted the test in the same place as the original.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-10 21:47 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-10 21:47 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java:283)
@davecramer I separated out the tests for empty vs null.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 13:09 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 13:09 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@SophiahHo please update all the tests where you removed "","" and add them back in. Keep the null, null but removing coverage doesn't seem like the right thing to do
Also who is the company you are working for ?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 19:26 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 19:26 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java)
As we update code, can you change this to use try with resources and get rid of the closeDB below ?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 19:26 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 19:26 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java)
Use try with resources
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 19:28 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 19:28 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc4/DatabaseMetaDataTest.java)
fix the error message to say noprocedures
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 19:28 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 19:28 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/test/java/org/postgresql/test/jdbc4/DatabaseMetaDataTest.java:345)
fix error message
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 19:29 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-11 19:29 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Once we fix the code can you also do the release notes for this please
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-11 21:36 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-11 21:36 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Do you mean run `release_notes.sh`? I'm using Windows Subsystem for Linux (WSL) to run shell scripts, and I ran into an issue compiling a Perl module in WSL that the script uses.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 10:13 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-12 10:13 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
No, I mean explain what the changes are in the commit message.
Thanks!
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 14:52 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-12 14:52 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Changes:
- For DatabaseMetaData methods, the `catalog` argument filters the results by catalog: it must match the current database name or be null to return non-empty results.
- For DatabaseMetaData methods, the returned ResultSet populates the current database name to columns like TABLE_CAT, TABLE_CATALOG, FUNCTION_CAT, PROCEDURE_CAT, PKTABLE_CAT, FKTABLE_CAT, TYPE_CAT.
- For DatabaseMetaData methods, empty strings for the following arguments can filter out results: `schemaPattern`, `tableNamePattern`, `columnNamePattern`, `functionNamePattern`, `procedureNamePattern`, `table`, `schema`, `primaryTable`, `foreignTable`, `primarySchema`, `foreignSchema`, `primaryCatalog`, `foreignCatalog`.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 16:16 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-12 16:16 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java:1195)
I hadn't seen this until now. I would think one should be able to use SPECIFIC_NAME to refer to an object in the database, no? This would create a name such as 123_somefunction which while unique can't be used to find the function.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 16:29 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-12 16:29 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java:1195)
@davecramer I did not add or update line 1194/1195. This is existing code.
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 17:07 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-12 17:07 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
(on pgjdbc/src/main/java/org/postgresql/jdbc/PgDatabaseMetaData.java:1195)
you are correct. thanks
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 17:08 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-12 17:08 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
I'd still be curious who the company is ?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 17:36 "SophiahHo (@SophiahHo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: SophiahHo (@SophiahHo) @ 2024-12-12 17:36 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer Thanks for merging. I work at [Precisely](https://www.precisely.com/).
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2024-12-12 17:43 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2024-12-12 17:43 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
You are welcome, thanks for hanging in there :)
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2025-02-21 04:13 "vnobo (@vnobo)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: vnobo (@vnobo) @ 2025-02-21 04:13 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Very slow, very slow, for this investigation for a day, it is here
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2025-02-21 13:14 "davecramer (@davecramer)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: davecramer (@davecramer) @ 2025-02-21 13:14 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
> Very slow, very slow, for this investigation for a day, it is here
Please, please elaborate. I have no idea what you are trying to say here ?
^ permalink raw reply [nested|flat] 33+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value
@ 2025-02-25 13:47 "kdebski85 (@kdebski85)" <[email protected]>
31 siblings, 0 replies; 33+ messages in thread
From: kdebski85 (@kdebski85) @ 2025-02-25 13:47 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
@davecramer
[vnobo](https://github.com/vnobo) probably meant the performance regression in 24.7.5.
Please see https://github.com/pgjdbc/pgjdbc/issues/3505
> > Very slow, very slow, for this investigation for a day, it is here
>
> Please, please elaborate. I have no idea what you are trying to say here ?
^ permalink raw reply [nested|flat] 33+ messages in thread
end of thread, other threads:[~2025-02-25 13:47 UTC | newest]
Thread overview: 33+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-09-26 20:29 [pgjdbc/pgjdbc] PR #3390: Fix PgDatabaseMetaData implementation of catalog as param and return value "SophiahHo (@SophiahHo)" <[email protected]>
2024-09-26 21:47 ` "svendiedrichsen (@svendiedrichsen)" <[email protected]>
2024-09-27 13:01 ` "davecramer (@davecramer)" <[email protected]>
2024-09-27 15:03 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-09-27 15:03 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-10-01 13:24 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-10-03 14:14 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-10-04 15:05 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-10-15 13:54 ` "davecramer (@davecramer)" <[email protected]>
2024-10-17 15:07 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-10 14:56 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-10 18:17 ` "davecramer (@davecramer)" <[email protected]>
2024-12-10 19:45 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-10 20:53 ` "davecramer (@davecramer)" <[email protected]>
2024-12-10 21:47 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-11 13:09 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 19:26 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 19:26 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 19:28 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 19:28 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 19:29 ` "davecramer (@davecramer)" <[email protected]>
2024-12-11 21:36 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-12 10:13 ` "davecramer (@davecramer)" <[email protected]>
2024-12-12 14:52 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-12 16:16 ` "davecramer (@davecramer)" <[email protected]>
2024-12-12 16:29 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-12 17:07 ` "davecramer (@davecramer)" <[email protected]>
2024-12-12 17:08 ` "davecramer (@davecramer)" <[email protected]>
2024-12-12 17:36 ` "SophiahHo (@SophiahHo)" <[email protected]>
2024-12-12 17:43 ` "davecramer (@davecramer)" <[email protected]>
2025-02-21 04:13 ` "vnobo (@vnobo)" <[email protected]>
2025-02-21 13:14 ` "davecramer (@davecramer)" <[email protected]>
2025-02-25 13:47 ` "kdebski85 (@kdebski85)" <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox