3 ms·
It's a lot of ceremony for not a lot of convenience. See: http://slick.typesafe.com/doc/1.0.1/lifted-embedding.html#inserting http://slick.typesafe.com/doc/1.0
by TylerE 13y 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#inserting 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.
- trailfox 13y agoIt also supports raw SQL...
- terhechte 13y agoThat goes beyond what it was created for. If you need sql to do anything useful, you can just as well not use a ORM.
- saryant 13y agoUsers.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).
- TylerE 13y agoTHe 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.