Hacker News new | ask | show | jobs
by TylerE 4625 days ago
It's a lot of ceremony for not a lot of convenience.

See: http://slick.typesafe.com/doc/1.0.1/lifted-embedding.html#in... and notice how much is involved in doing a simple insert into a table with a primary key.

2 comments

  Users.forInsert insert User(None, "Christopher", "Vogt")
Personally, I don't find that to be a lot of ceremony. Now, Slick definitely still has some problems and requires too much boilerplate, I'll certainly agree with that but I don't think this is one of those cases (though it could be improved).
THe ceremony is creating the "for insert" facade. To me the logical thing to do would be for Slick to have an "AutoInc Int/Long" type that is implicitly convertable from Option, so that you could just do a normal insert and the the None value just causes the id column to be omitted.
It also supports raw SQL...
That goes beyond what it was created for. If you need sql to do anything useful, you can just as well not use a ORM.