When we insert we usually want the new row back, so let’s do that. sql'update person set age = 15 where name = 'Alice''.() case class Person(id: Long, name: String, age: Option) Insert1('Bob', None).quick.unsafeRunSync() // switch to YOLO modeĪnd read them back. insert1('Alice', Some(12)).run.transact(xa).unsafeRunSync() Sql'insert into person (name, age) values ($name, $age)'.update def insert1(name: String, age: Option): Update0 = Here we define a method that constructs an Update0 that inserts a row into the person table. Inserting is straightforward and works just as with selects. (drop, create).mapN(_ + _).transact(xa).unsafeRunSync() We can compose these and run them together, yielding the total number of affected rows. quick gives a IO that prints out the row count. run method gives a ConnectionIO that yields the total number of rows modified, and the YOLO-mode. This looks a lot like our prior usage of the sql interpolator, but this time we’re using update rather than query. Let’s create a new table, which we will use for the examples to follow. It is uncommon to define database structures at runtime, but doobie handles it just fine and treats such operations like any other kind of update.

See Logging page for how to log events in detail LogHandler = None // Don't setup logging for now. Password = 'password', // Database password Url = 'jdbc:postgresql:world', // Connect URL - Driver specific Val xa = omDriverManager(ĭriver = '', // JDBC driver classname See the chapter on connection handling for more info. A transactor that gets connections from and executes blocking operations Setting UpĪgain we set up a transactor and pull in YOLO mode, but this time we’re not using the world database. In this chapter we examine operations that modify data in the database, and ways to retrieve the results of these updates.

Postgresql insert many rows