SQLDelight VS OkHttp

This seems to be similar to https://github.com/cashapp/sqldelight, and I've always wanted a python equivalent!

In typescript, there are query builders (not talking about ORMs) that can basically do this within the type system, but that would be infeasible in python's type system. This approach (type/code generation is a good alternative, though I like using sqlalchemy / alembic to manage schemas/migrations.

One thing I'm curious about is how it knows the types of columns? I looked quickly at the Readme but didn't see it (probably a parameter somewhere I missed).

That functionality has existed for almost exactly a year

- SQLDelight - great experience overall, the only issue that I found, was when that I made a database migration that worked on Android, but not on iOS (https://github.com/cashapp/sqldelight/issues/3812)

Database - SQLDelight

room is a great example but like I said our data is kotlin-only so we tend to use libraries like sqlDelight.

This seems similar to https://cashapp.github.io/sqldelight/ for kotlin, I think this approach is pretty neat, good luck with it!

Sounds like you want what SQLDelite offers, but for TypeScript. SQLDelite is only for Kotlin and SQLite though.

SQLDelight had neat built in support for this

https://cashapp.github.io/sqldelight/

You would really like sqldelight[1] then. It takes the concept of an ORM and flips it on its head. Instead of mapping function calls to SQL statements, it lets you write SQL statements and then generates classes for you that have methods for those statements.

For instance, you could have a SQL statement like getCardsForFight: select * from fights where cardId = ? and titleFight = ?, and it would generate a class that has a method getCardsForFight(cardId: number, titleFight: number).

[1]: https://github.com/cashapp/sqldelight

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp