Constraints: a Developer's Secret Weapon Thursday 15:40 New York
Twitter: @leinweber Blog: bitfission.com GitHub: will Company website: www.citusdata.com
Hi, I’m Will. I’m coming from San Francisco, and I’ve been working on hosted postgres services for a while now, currently at Citus Data.
I mostly attend and speak at conferences, not so much on the mailing lists.
This will be my seventh pgconf.eu conference. I did fosdem once but it was too crowded for me, so I’m not sure about that one. I really appreciate how the .eu conference moves around each year as a visitor.
It’s about all the good things that come from adding restrictions and constraints to your database, and treating it as the last line of defense for bugs and bad data. I think it’s important because a lot of application developers tend to treat the database as just a place to store and retrieve information, and even just a few constraints can go a long long way to a healthier and more resilient application.
Application developers.
Nothing too much, anyone using postgres for their application should be good.
Channel binding for scram, which really makes it a good feature. Though I need to add scram support for my crystal language driver.
I saw "Cleaning out crocodiles teeth with PostgreSQL indexes - a story on all the index types in PG" at the recent conference in San Francisco, and it was very good. I’d like to check out Heikki’s server side C talk also.