Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aliases do not carry proper metadata. #2981

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

garydgregory
Copy link

Add a failing test to show that an ALIAS to a Java method does not carry any parameter metadata. Internally the type is unknown which is then mapped to 12 (VARCHAR).

I'm not sure the best way to fix this. I am looking for help from the community here.

any parameter metadata. Internally the type is unknown which is then
mapped to 12 (VARCHAR).
@grandinj
Copy link
Contributor

Yeah, we don't support that kind of metadata at all.

What is your broader use-case for this?

@garydgregory
Copy link
Author

Hi all,
I am working on a set of tools and a runtime that rely heavily on metadata using mostly MySQL and DB2 but we also test with H2, MS-SQL Server and Oracle. In fact, initial development and tests is often done using H2 since it is so convenient. We are now implementing some new feature around stored procedures and arrays. I can no longer use H2 for this work. So if H2 has no plans on supporting these JDBC APIs, I'll have to go to one of our main DBMSs.

@katzyn
Copy link
Contributor

katzyn commented Dec 17, 2020

Current H2 (compiled from the current sources) provides this information in standard INFORMATION_SCHEMA.ROUTINES, INFORMATION_SCHEMA.PARAMETERS,
INFORMATION_SCHEMA.ELEMENT_TYPES (for arrays) and other tables.

Unfortunately, only some DBMS support SQL/Schemata properly.

@katzyn
Copy link
Contributor

katzyn commented Dec 17, 2020

On the other hand, callable statements have only very basic implementation in H2. They are rarely used, so nobody carried about their metadata.

@garydgregory
Copy link
Author

garydgregory commented Dec 17, 2020

On the other hand, callable statements have only very basic implementation in H2. They are rarely used, so nobody carried about their metadata.

I think it would be helpful to think about this in the context of JDBC users and not H2 users. In my case, I use H2 as a placeholder for other databases and as a convenience during development. Saying that callable statements are rarely used in H2 might be true (how would you know?), but it is certainly not the case for the JDBC applications I see.

@grandinj
Copy link
Contributor

Saying that callable statements are rarely used in H2 might be true (how would you know?), but it is certainly not the case for the JDBC applications I see.

This is entirely a volunteer developed project, with nobody being paid to work on H2. If you don't like it, feel free to use another project or do the necessary work yourself.

@garydgregory
Copy link
Author

Saying that callable statements are rarely used in H2 might be true (how would you know?), but it is certainly not the case for the JDBC applications I see.

This is entirely a volunteer developed project, with nobody being paid to work on H2. If you don't like it, feel free to use another project or do the necessary work yourself.

I am surprised to see such a negative and dismissive attitude here, quite sad in fact. Over at Apache Commons, Apache HttpComponents, and Apache Log4j, where we are in the same FOSS boat, I'd like to think that I and my fellow volunteers do our best to welcome help, usually by asking for a pull request. Instead, what I read above is "go away". Nice touch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants