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

WARN [Datastore] java.lang.Double jdbc-type=FLOAT #1980

Closed
gray380 opened this issue Sep 26, 2022 · 2 comments
Closed

WARN [Datastore] java.lang.Double jdbc-type=FLOAT #1980

gray380 opened this issue Sep 26, 2022 · 2 comments

Comments

@gray380
Copy link

gray380 commented Sep 26, 2022

Hello,

Do I need to worry about the following warnings?

2022-09-26 19:21:58,464 INFO [UpgradeInitializer] Initializing upgrade framework
2022-09-26 19:22:00,068 WARN [Datastore] Default type for java type of java.lang.Float was previously jdbc-type=FLOAT but this is not provided by the JDBC driver! Please report this to the DataNucleus developers
2022-09-26 19:22:00,069 WARN [Datastore] Default type for java type of java.lang.Double was previously jdbc-type=FLOAT but this is not provided by the JDBC driver! Please report this to the DataNucleus developers
2022-09-26 19:22:03,613 INFO [PersistenceManagerFactory] Initializing persistence framework
2022-09-26 19:22:03,797 WARN [Datastore] Default type for java type of java.lang.Float was previously jdbc-type=FLOAT but this is not provided by the JDBC driver! Please report this to the DataNucleus developers
2022-09-26 19:22:03,798 WARN [Datastore] Default type for java type of java.lang.Double was previously jdbc-type=FLOAT but this is not provided by the JDBC driver! Please report this to the DataNucleus developers

Environment:

  • Dependency-Track Version: 4.5.0
  • Distribution: [ Docker ]
  • BOM Format & Version:
  • Database Server: [ MSSQL ]
  • Browser: Opera
@nscuro
Copy link
Member

nscuro commented Sep 28, 2022

Hi @gray380, thanks for raising this.

I took a deeper look into this and the bottom line is: No, you don't need to worry about this.

This was previously reported to the ORM developers back in 2019 (datanucleus/datanucleus-rdbms#304). I just submitted a PR to the DataNucleus project that should resolve this warning: datanucleus/datanucleus-rdbms#451

This however has no functional impact on Dependency-Track. You can expect this warning to disappear in the next release, assuming my DataNucleus PR gets merged.

Closing this issue, as there's nothing for the Dependency-Track project to do.

@github-actions
Copy link
Contributor

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants