sqltyped maintenance

[binkabir]

Hi All, is sqltyped still actively maintained ?
Thanks

[jonifreeman]

Hi! It is not actively maintained at the moment. I still believe something like sqltyped is a good way to integrate with relational databases from a statically typed language. Unfortunately the
mainstream solutions tend to be query DSLs, ORMs and such.

I'm not developing sqltyped at the moment. The reason being that my current client is not using Scala (not
my choice). I hope I can work with Scala again at some point but the time will tell... I will help by answering questions about the current code and giving opinions on design decisions if anyone decides to fork this and continue development.

One option which you might evaluate too is Slick. It is backed by Typesafe and is therefore "safer" solution with more guaranteed longevity. Slick will include type inference feature too. Please see slides 74 and 75:

http://slick.typesafe.com/talks/2014-09-24_ScalaCamp/Introduction_to_Slick_2.1_and_2.2.pdf

A big difference with Slick's approach is that they return rows as tuples whereas sqltyped returns rows as records. The former loses column names and that's information which is sometimes nice to have when
processing the result set. But then, sqltype's choice to use records (which must be emulated with HLists as Scala does not have a native record system) comes with a potential caveat. Compiling code which
processes big records (records having many fields that is) may result in very bad compilation times.

Cheers!

[binkabir]

Hi jonifreeman, Im playing around with Slick 3.0, averagely its looks good my only challenge is writing join statements of 3 or more tables, it becomes ugly and difficult. My thoughts was to look for a scala sql library that is good at plain queries(that returns rows as records) for queries that I find complex in slick