Ivan

This issue should be updated to "Support Backup/Restore PostgreSQL 17" now.

Hey @FlorianWilhelm, thanks for another thoughtful reply. I have no doubt that enforcing the predefined structure is way more in line with software engineering best practices. I was mostly concerned...

Hey there @FlorianWilhelm, I didn't try to use `get_db`. What I did try was just accessing the `schema` property of the `Database` objects returned by `Page.subdbs`, as I saw the...

There is indeed a bug with two-way relations when performing reflection. In the code below, it doesn't matter whether I uncomment the commented line (thus performing the reflection via `get_db`)...

Unfortunately not, @FlorianWilhelm. I was running it from main. I just tested it again using 5a1d4e6687436824222b2ad4d0d8bdc1ae7a6ac6 (`uno info` shows `0.9.4.post1.dev12+g5a1d4e668`), and the error still happens.

Dang, you're right! 🤦‍♂️ I copied the example straight from [the docs](https://ultimate-notion.com/0.9/usage/db_advanced/#two-way-self-relations) and didn't notice the attribute name doesn't match the property name. Simply changing the attribute name to `items_purchased`...

Hey @FlorianWilhelm! Indeed, assigning to `attr_name` is already mentioned in [Programmatic way of defining a schema](https://ultimate-notion.com/0.9/usage/db_advanced/#programmatic-way-of-defining-a-schema). And I did remember seeing that in the docs, but the actual problem was...