You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
Hello,
Do I need to worry about the following warnings?
Environment:
The text was updated successfully, but these errors were encountered: