Skip to content

miscellaneous 72 stable prod fixes (Postgres)#1206

Open
JesseChavez wants to merge 3 commits into
jruby:72-stablefrom
JesseChavez:72-stable-prod-fixes
Open

miscellaneous 72 stable prod fixes (Postgres)#1206
JesseChavez wants to merge 3 commits into
jruby:72-stablefrom
JesseChavez:72-stable-prod-fixes

Conversation

@JesseChavez

Copy link
Copy Markdown
Contributor

Hi JRuby team

Here is some miscellaneous fixes the we found and fixed in my fork

Notes I only cherry-picked Postgres fixes and I have not tested in SQLite and MySQL

hope casting the binds is not affecting MySQL or SQLite

@enebo

enebo commented Dec 13, 2025

Copy link
Copy Markdown
Member

@JesseChavez Do you have any idea on the massive regression on postgresql tests? I do not think it has anything to do with your PR but we seem to no longer be closing active connections (at least in some case). I mean maybe we are raising on some type binds but not cleaning stuff up but obviously not running a job since september on 72-stable is the most likely culprit.

if ( value == context.nil ) {
statement.setNull(index, type);
// statement.setNull(index, type);
statement.setObject(index, null);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

have you considered only fixing this for PG, if that is an actual concern?

would be nice to have a failing test case to see if this isn't hiding another issue, would be surprised if a mature JDBC driver would not handle setNull properly

// }
// }

statement.setObject(index, value.asString().toString(), Types.OTHER);

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

seems risky to change this, not sure if the included test case related to this?

@headius

headius commented Jun 27, 2026

Copy link
Copy Markdown
Member

I've started working with @skunkworker to merge in a bunch of LLM-created changes to bring us more in parity with the 7.2 and 8.1 Rails adapters, with a specific focus on PG. Please coordinate with him and try to figure out which changes make sense to pull from here.

I know we've lagged behind keeping up the PG adapter, but with the knowledge you both have of PG behavior and assistance from some tooling I think we can rapidly catch up.

@JesseChavez

Copy link
Copy Markdown
Contributor Author

Hi @headius

we have branch with all the changes and fixes to support Rails 8.0 for postgres. At the moment we are working fixes for sqlserver.

Are you guys in interested on this work ?

@headius

headius commented Jun 28, 2026

Copy link
Copy Markdown
Member

Hi @headius

we have branch with all the changes and fixes to support Rails 8.0 for postgres. At the moment we are working fixes for sqlserver.

Are you guys in interested on this work ?

Absolutely! @skunkworker also submitted an attempt at auto generating 8.1 support but there's a number of concerns about duplicated code and tests. Anything that moves us further away from calling reusing Rails core code will just be harder to maintain long-term. Let's see what you've got and try to combine all of our efforts to get updated drivers out.

@JesseChavez

Copy link
Copy Markdown
Contributor Author

Thanks

the PR will be ready for tomorrow Australian Time

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.

4 participants