On Tuesday, September 24, 2013 5:02:30 PM UTC-4, Lukas Eder wrote: > > > 2013/9/24 Rob Nikander <[email protected] <javascript:>> > >> >> Are you using SQL Server Express, then? Because with a regular SQL Server > license, I don't think that some additional money would be an issue, right? > And why didn't you ask for the price, I'd be curious, myself ;-) >
Good point; I just asked. It's probably not much money. Yes this project uses one of the cheaper editions. There are other factors though... sometimes you work on a project as a contractor and the database decision has already been made, and paid for by someone else. And sometimes the use of Scala is seen as a bit "fringe" so you don't want to start talking about monthly fees and get put back in Java land. > >> Even on a fresh project I think I'd use jOOQ or something similar in >> Scala. I appreciate the purity in Slick, eg: a filter is always a filter, >> not a "where" or "having" depending on it's location. >> > > That's interesting. So the filter's "where" or "having" semantics depends > on where it's placed, lexicographically? What about "connect by" filters? > Or boolean values (put in projections, such as SELECT 1 = 2)... > I didn't get that deeply into it, and should let someone who knows Slick better answer that. My impression was that they want to stay in functional programming land, where `filter` takes a sequence and a predicate, and that's all you need to know. Let the compiler choose a 'where', 'having', nested select, whatever, as needed, under the hood. I'm not bothered enough by SQL to gamble on that. I think that a more formal distinction between "where" and "having" is > important, as such things will make SQL transformation quite hard, when > more advanced SQL features are used, e.g. GROUPING SETS. Although, I don't > think that's a priority for SLICK right now. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
