reader VS sqlc

I like this pattern so much, I wrote an article about it; if you want to see what it looks like in real life, check this out.

It can also be used to build bookmarking / read later functionality similar to that of Tiny Tiny RSS; extracting content from arbitrary pages would be pretty helpful here.

To find out more, check out the GitHub repo and the docs, or give the tutorial a try.

[1]: https://death.andgravity.com/query-builder-how#more-init

[2]: https://github.com/lemon24/reader/blob/10ccabb9186f531da04db...

Looking now through the Python API docs, I found the Quoting characters for use in search thing, which may come in handy for something I'm doing for my feed reader library (deduplicating articles). Not sure if I'll vendor it or add sqlite-utils as a new dependency, but it's good to know someone already solved this problem (I have a prototype, but I haven't really tested it).

I'm happy to announce version 2.0 of reader, a Python RSS / Atom / JSON feed reader library.

I'm also working on the 2.0 version of my feed reader library. The backwards compatibility break allows me to clean up a bunch of unnecessary code and fix some bad design decisions; I've deleted 250 lines of code until now, and it's very satisfying.

The exact same problems None has when it's not a valid value. None is different from the variable type, that's why you have Optional[VarType], which is an alias for Union[VarType, None]; you can model this in exactly the same way: Union[VarType, MissingType]; here's an example.

reader is a Python feed reader library – it offers all the high-level things you'd want when making a feed reader app/website, except the actual web app.

"Is there a way to get sqlc to use pointers for nullable columns instead of the sql.Null types?"

I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.

Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).

Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.

sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.

I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.

Now, we are going to generate the code. For this purpose, we are going to use sqlc.

https://github.com/sqlc-dev/sqlc — for use with //go:generate