Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Kemal Durmus
    @mkemaldurmus
    I want to do an upsert operation with edpoint. If merhantId is null it will insert, otherwise cpcValue will update.
    1 reply
    David-hod
    @David-hod
    using slick with postgress DB. I have instant field on scala and 'TIMESTAMP WITH TIME ZONE' on postgress. it seems like it is not the exact time before persiting and after loading from DB. any suggestionns?
    Felipe Bonezi
    @felipebonezi
    hey guys, how can I filter a Option[LocalDate] if it's greater than another LocalDate?
    1 reply
    Ali Ustek
    @austek
    @felipebonezi have you tried
    def filter(date: Option[Instant] = None)= { tableQuery.filter { item => List( date.map(item.updatedAt > _) ).collect({ case Some(criteria) => criteria }).reduceLeftOption(_ && _).getOrElse(true: LiteralColumn[Boolean]) }.result }
    SynappsGiteau
    @SynappsGiteau
    Hi everyone, is there a possibility with slick to add an automatic filtering on all queries?
    Usecase: in a multi-tenant application, with an implicit value, it would be interesting not to have to worry about this filtering when we make our queries.
    Anyone have an idea?
    4 replies
    Arsene Tochemey Gandote
    @Tochemey
    Hello folks how can I get a JdbcBackend database instance from JdbcProfile
    AIIIN
    @AIIIN

    Hey guys,
    I am currently using like to filter my rows, but somehow I can not manage to do it when the column contains Long values. Here is some code:

    val term: String = "some string"
    val searchTerm: String = s"%${term.toLowerCase}%"
    ...
    (...).filter(r =>
                (r._1._1._1.text.toLowerCase like searchTerm) ||        // works
                (s"%${r._1._1._1.Id}%" like searchTerm)                 // does not work
           )

    In the second like query the compiler sais Cannot resolve symbol like.
    I also tried (r._1._1._1.Id.toString like searchTerm) but that gives me the same error...

    AIIIN
    @AIIIN
    Found it! You need to pass the column as String:
    r._1._1._1.Id.asColumnOf[String] like searchTerm)
    amahonee
    @amahonee
    Hi Guys, is there a nice way/ is it possible to batch a Set[FixedSqlAction[Int, NoStream, Effect.Write]] into a single db.run{...} call? Thanks in advance
    Heikki Vesalainen
    @hvesalai
    @amahonee sequence them (see DBIOAction.sequence)
    (there is also seq and fold)
    Daniel Robert
    @drobert
    fold has some stack-size limitations though. e.g. if you fold 10,000 || operations together you can end up with stackoverflow
    hmm, I suppose I'm thinking more of reduce, per slick/slick#1606
    amahonee
    @amahonee
    Hey guys thanks for the help on the last issue I had! I have a question regarding updating a jsonb column. I have a Set[(Instant, Option[Instant]] for describing an IDs active periods. Is it possible to access this set to update a None value when it is deactivated and modify the column in one db action?
    I want to read the value from the DB, perform actions on it, and reinsert it into the DB with an table.update(). Thanks again in advance
    Nikhil Arora
    @nikhilaroratgo_gitlab
    Hello Guys, I am using Lagom 1.6.4 and Java with PostgreSql. I want to read data from DB in a akka Streamed way ie. Create a Source for some Select query. Is there are way to get a akka stream Source ? I found that alpakka-slick is one way and I am currently experimenting with that. It works but it creates its own Hikari pool and I want to avoid that. I used SlickSession.forConfig("slick-postgres" and then Slick.source(session,query,mapper). Any suggestions on this please. Thanks
    2 replies
    oybek
    @oybek

    Hello Guys!
    I couldn't find any answer in slick documentation https://books.underscore.io/essential-slick/essential-slick-3.html (perhaps my poor search skills)
    My question is, I have the following query construction:

    messages.filter(_.sender === "Dave")

    But in practice folk does

    messages.filter(_.sender === "Dave".bind)

    What is the difference and why is it motivated to do so?
    I tinkered a little in REPL with slick, and that is all I've got:

    scala> messages.filter(_.sender === "Dave").result.statements.toString
    res7: String = List(select "sender", "content", "id" from "message" where "sender" = 'Dave')
    
    scala> messages.filter(_.sender === "Dave".bind).result.statements.toString
    res8: String = List(select "sender", "content", "id" from "message" where "sender" = ?)

    In the first case we got query with static injected value in it, it is in '' and I think there is no danger of sql injection.
    In second scenario we've got just placeholder, in this case when the values are actually will be inserted in query?
    why the second case with .bind preferable?

    Sorry for my terrible english with a lot of syntax error's

    Richard Dallaway
    @d6y
    I think the bind version is, in principle, reusable (for different values) by the database/jdbc-land. That would save the database from making a new queey plan for each call. In practice, I don’t know if that actually happens. I’m hoping others can confirm/refute that.
    Queey? Query plan, I mean!
    oybek
    @oybek
    How can I reuse and substitute different value is such a case?
    1 reply
    micky44
    @Micky44Scoll_twitter
    Have slick support scala 3?
    nafg
    @nafg
    @oybek a while ago, @szeiger made a scala 3 version but I don't think I got merged or published
    Sorry that was for @Micky44Scoll_twitter
    Seth Tisue
    @SethTisue
    @nafg @Micky44Scoll_twitter the Scala 3 PR has been revived at slick/slick#2187 — I'm not sure how close to complete it is
    if you think you might have any spare time to help out, please subscribe to that PR (and/or slick/slick#2177) and keep an eye out for opportunities to help keep it moving
    Seth Tisue
    @SethTisue
    oh btw anyone interested in the future of Slick might also be interested in:
    also slick/slick#2169 about updating versions of the database connectors
    Seth Tisue
    @SethTisue
    looks like we're on track for a 3.4.0 release, maybe in April?
    nafg
    @nafg
    @SethTisue anything I can do to help?
    Seth Tisue
    @SethTisue
    @nafg absolutely, please help review pull requests! including perhaps adopting and resubmitting abandoned ones if the original person has disappeared
    and test an RC once we have one
    and help the Scala 3 guy if he needs it, that one is huge. it isn't clear yet what kind of help he might need
    help re-enabling Appveyor so we don't regress on Windows would be awesome: slick/slick#2178
    (or use GitHub Actions for Windows testing.... either way)
    perhaps there are other important tickets that I don't even recognize the importance of because I know nothing about Slick. I'm engaging with it just as generic Scala OSS
    we'll roll an RC as soon as the current round of PRs finishes landing
    once there's an RC I'm going to do a round of publicity (on Twitter, Discourse, Reddit, and so forth) in the hopes of attracting testers and others kinds of help
    nafg
    @nafg
    @SethTisue any kind of timeline? I'd love to help but right now is not great
    Seth Tisue
    @SethTisue

    @nafg I think we'll be ready to do an RC in about two weeks, and then after that wait a month or so, minimum, before final? maybe longer depending on how the RC is received?

    but also, I'm not just trying to get one release out, I'm hoping this can be self-sustaining again going forward, for as long as people are still using the library

    nafg
    @nafg
    Ok my time is limited right now but if anyone wants to do a video call with me it could happen sooner
    nafg
    @nafg
    @SethTisue do you have any interest?
    Seth Tisue
    @SethTisue
    @nafg sure — write me at seth dot tisue at lightbend dot com and we can set it up. I'm not exactly sure what you have in mind or if I can help, but talking never hurts :-) I'm in Nevada/California time zone and free most weekday mornings
    James Phillips
    @jdrphillips
    I'd like to write my own DatabaseAction that does a special thing. But it doesn't seem it's possible as Database.run won't anticipate it. Is that correct?
    Richard Dallaway
    @d6y
    Yeah, that looks right @jdrphillips -- DBIOAction is a sealed trait. What do you want to achieve? There's likely another way we can try to think up!
    James Phillips
    @jdrphillips
    DBIOAction is sealed but DatabaseAction is not, so I hoped it may have been possible to sneak something in

    What do you want to achieve?

    I wanted to implement something like "clean up" actions. Attach an effect to your DBIO, and carry it around with you across all the flatmaps/andthens etc, and then when it is eventually run tack the effects on to the future as a side-effect.

    Imagine something like a huge dbio transaction that at some point changes a user's subscription settings. At that point in the DBIO, I know I have to send an email to the user. It would be handy to at that point attach it (the send-email effect) to the DBIO and have it dealt with alongside the transaction execution automatically (if the transaction succeeds)

    It's probably something to do properly on top of slick, I know that - but everything is already a DBIO in our code and I wanted an easy way to slip it in, that's all :)
    James Phillips
    @jdrphillips
    (I could of course turn the email-effect into a future and then into a DBIO and have it sit in the middle of the DB transaction but I don't want to do that)
    Richard Dallaway
    @d6y
    I wonder if cleanUp or andFinally on an action are a place you could do some of that.
    James Phillips
    @jdrphillips
    andFinally seems to inject things into the middle of the DBIO structure, rather than keeping them at the end. From my understanding anyway. So if we ended up rolling the transaction back the email would be sent in error
    I admit I didn't look too closely at cleanup as it seemed to be about errors but I'll have a closer look