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

Support for Slick 3.4.0-M1 #122

Open
oschrenk opened this issue May 13, 2022 · 5 comments
Open

Support for Slick 3.4.0-M1 #122

oschrenk opened this issue May 13, 2022 · 5 comments

Comments

@oschrenk
Copy link

oschrenk commented May 13, 2022

I am currently working on a project that makes extensive use of Slickless 0.3.6 with Slick 3.3.3. That project wants to move to Scala 2.13 and has some strict compiler flags set that will fail because of the code emitted by slick

See also slick/slick#2121 and slick/slick#2054

They seem to be addressed in release 3.4.0-M1. Unfortunately I can't move to that since slickless depends on 3.3

Do you plan of supporting the 3.4 series?

@oschrenk oschrenk changed the title Support for 3.4.0-M1 Support for Slick 3.4.0-M1 May 13, 2022
@nafg
Copy link

nafg commented May 15, 2022

I doubt anything relevant changed, so you could just use them together and silence any sbt eviction warnings. By the same token Slickless should be able to publish just by updating the slick version and no other code changes.

@oschrenk
Copy link
Author

Thanks! That's a good idea - I have not tried that.

@nafg
Copy link

nafg commented Sep 12, 2022

3.4.0 was released.

Is there a reason Scala Steward is not really being used?

@dejvid
Copy link

dejvid commented Jun 30, 2023

I would like to use it with Scala 3.3. Looks like the project is abandoned are there and alternatives? I think scala 3 doesn't have this limitation—no HList is required.

@nafg
Copy link

nafg commented Jun 30, 2023

@dejvid this issue is not really the place to discuss.

Anyway, even without slickless and scala 3 you can use Slick with nested tuples or nested case class projections. I guess if you're code-generating from tables with lots of columns that would be harder to do (though it might be easier with my code generator in slick-additions than the built in one)

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

No branches or pull requests

3 participants