No upcoming presentations...

    There is no protection against bad queries. If a query is poorly written, it's execution can't be improved with any indexes, fast access path or other database advancements. What is the most common source of poorly written queries? Most of the time they do not come from humans; they are generated by applications that use ORMs to communicate with databases. What can we do to prevent it from happ...

    @ Postgres Conference 2020
    Development

    If there is one thing that can be learned from a generation of ORM frameworks, it is that treating a database like a fancy hashtable does not work, yet this is exactly what most entity-managers will do! In a proverbial sense, one can imagine that the problems of impedance mismatch are akin to those experienced when taking a Commanche helicopter and racing it around a Formula-1 race track agains...

    @ Postgres Conference 2020
    Development

    SQL Queries can get large, really, really large. Typically this complexity is attacked using stacked SQL views or ORM frameworks like Hibernate, which both have major limitations. SQL itself has no objects so constructs more abstract than a View are unavailable, making programming graces like polymorphism all but a dream. ORM, on the other hand, comes at the cost of notorious impedance mismatch...

    @ Philly 2019

    Jul 19 2019

    Dev