Nostr SQL databases

[yukibtc]

Adds support for PostgreSQL, MySQL and SQLite backends.

[yukibtc]

@tompro, during local tests, I noticed that diesel requires the database URL for generating the rust schemas. Do you know if there is a way to generate schemas without have to connect to the database?

I found also sqlx, which also supports multiple backends, like diesel. Have you ever tried it or are you aware of the differences?
The nice thing of diesel is that, theoretically, supports SQLite for WASM, while sqlx doesn't seems to support WASM.

[tompro]

@tompro, during local tests, I noticed that diesel requires the database URL for generating the rust schemas. Do you know if there is a way to generate schemas without have to connect to the database?

You probably mean for generating/updating the rust bindings (ORM mappings)? The thing is in Diesel this is done reverse. So first you run your migrations in a db instance and then re-import the bindings (diesel print-schema). This approach allows you to import a foreign schema from an existing db but it always requires a running database.

I found also sqlx, which also supports multiple backends, like diesel. Have you ever tried it or are you aware of the differences? The nice thing of diesel is that, theoretically, supports SQLite for WASM, while sqlx doesn't seems to support WASM.

I have been using sqlx but it is a low level driver where you mostly write queries in native SQL as there are no rust bindings. With the 'new' goal of supporting multiple databases I might have chosen to use it anyhow as there are almost no generics and derives involved. I think they even have code triggered migrations now. There is also SeqQL which puts a ORM on top of sqlx but when I checked it out last time it was not even close to Diesel.

[cesardeazevedo]

It would be nice if we could return a async iterator here and let nostr-relay-builder consume it without allocating all the events in memory.