{"uri":"https://octothorp.es/","term":"api","thorpes":[{"uri":"https://justatheory.com/2024/06/abi-api-guidance/","title":"Patch: Postgres ABI and API Guidance","description":"Dear Postgres extension developers: Please review and give feedback on the proposed patch adding ABI and API guidance to the C language documentation."},{"uri":"https://justatheory.com/2022/08/rfc-restful-secondary-key-api/","title":"RFC: Restful Secondary Key API","description":"A RESTful API design conundrum and a proposed solution."},{"uri":"https://justatheory.com/2005/10/sqlite-perl-aggregates/","title":"Custom SQLite Aggregates in Perl","description":"About a year ago, Josh Berkus was reviewing some Bricolage SQL code, looking to optimize it for PostgreSQL. One of the things he noticed was that we were fetching a lot more rows for an object than we needed to. The reason for this is that an object might be associated with one or more groups, and to get back a list of all of the group IDs, we were getting multiple rows. For example, if I wanted to fetch a single story with the ID 10, I might get back rows like this:"}],"bookmarks":[]}