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

More code clean up to fix SonarQube issues #1977

Merged
merged 11 commits into from
Dec 22, 2022
Merged

More code clean up to fix SonarQube issues #1977

merged 11 commits into from
Dec 22, 2022

Conversation

lilgreenbird
Copy link
Contributor

@lilgreenbird lilgreenbird commented Nov 28, 2022

also some coding standard fixes

@lilgreenbird lilgreenbird added this to the 12.2.0 milestone Nov 28, 2022
@lilgreenbird lilgreenbird changed the title More SonarQube warning fixes More code clean up to fix SonarQube issues Nov 29, 2022
lilgreenbird and others added 7 commits November 29, 2022 12:35
… over decremented (#1989)

* Updated onDone with reason/comment for unecessary decrement for future reference

* Added more ICR tests

* Added missing brackets

* Test table names needed to be unique

* Drop tables within test if exist

Co-authored-by: lilgreenbird <[email protected]>
* Merge dev to master for 9.2.0 release (#1506)

Merge dev to master for 9.2.0 release (#1506)

* fix merge

* Fix #1964 by not having a static field at all. It was cleared each time anyway.

* refactor a bit

Co-authored-by: ulvii <[email protected]>
Co-authored-by: Peter Bae <[email protected]>
Co-authored-by: Milan Mimica <[email protected]>
…ion to datetime or datetime2 (#1687)

* Added support for dateTimeType connection string

* Added support for the dateTimeType connection string, which allows you to define how date/time values are parameterized in SQL Server. By default, for SQL Server 2008+ the "datetime2" datatype is used, where as older versions of SQL Server always use the "datetime". This allows users migrating older database application that exclusively use "datetime" datatypes to run in SQL Server compatibility modes newer than 2014.
* Added unit test coverage for changes

* Renamed dateTimeType to datetimeParameterType

* Revert "Merge branch 'dev'"

This reverts commit 416dd5e, reversing
changes made to 4e8d787.

* Resolved merge conflicts

* Revert "Update versions to fix vulnerabilities (#1689)"

This reverts commit 4e8d787.

* Fixed broken merge and re-added datetimeParameterType feature

The merge was corrupted and blew out most of the datetimeParameterType feature changes, so I've re-applied the changes manually.

* Create Parameter.java

superficial change just to trigger pipeline run

* Delete SQLServerConnection.java.orig

this file should not be here

* Apply suggestions from code review

Co-authored-by: David Engel <[email protected]>

* Update src/main/java/com/microsoft/sqlserver/jdbc/Parameter.java

Co-authored-by: David Engel <[email protected]>

* Update src/main/java/com/microsoft/sqlserver/jdbc/Parameter.java

Co-authored-by: David Engel <[email protected]>

* Update src/main/java/com/microsoft/sqlserver/jdbc/SQLServerLexer.java

Co-authored-by: lilgreenbird <[email protected]>
Co-authored-by: David Engel <[email protected]>
/**
* internal class name used in tracing
*/
private static final String INTERNAL_CLASSNAME = "SQLServerStatement";
Copy link
Member

@tkyc tkyc Dec 22, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can just use SQLServerStatement.class no? No need to define a string (I saw another place that did this too in the PR)

@lilgreenbird lilgreenbird merged commit 8f5f9da into main Dec 22, 2022
@Jeffery-Wasty Jeffery-Wasty mentioned this pull request Jan 30, 2023
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.

5 participants