SQLProvider VS TypeORM

For completeness, there is also the SqlDataProvider, which I only tried out a little years ago, before composibility was baked in. Worth a look.

Have you heard of type providers? https://fsprojects.github.io/SQLProvider/ I think this library might be what you are looking for

Database: SQL or Event Store. If SQL, One of https://fsprojects.github.io/SQLProvider/, https://github.com/Dzoukr/Dapper.FSharp or https://github.com/SQLStreamStore/SQLStreamStore

One of the more popular Type Providers I used is the SQL Provider, but even it has severe limitations when it comes to .NET Core.

There was a wave of popularity in 2017 as well. I used to work on it full time back then, and enjoyed it a lot. The SQLProvider [0] and other type providers like it are super impressive!

[0] https://fsprojects.github.io/SQLProvider/

(1) F# Type Providers still blow my mind.

Strongly typed SQL/XML/CSV/JSON without boilerplate is a massive leap forward, and it's a shame that it hasn't caught on.

https://fsprojects.github.io/SQLProvider/#Example

Like this?

So... I'm a little bit lost here. I must say, I love this language, but documentation is definitely not its greatest strength. I've looked at the SQLProvider documentation and found no information. Then I looked through the repository issues and found a lot of people with similar issues and, even though they should theoretically be solved with version 1.2, I tried doing what ended up working for them, with little luck. I've tried different combinations of library targets and dependencies versions but none worked.

So when I clone a typical open source F# project from GitHub (e.g. SQLProvider, to pick a recent one that I wrestled with), I'm often at a loss how to build and debug the thing. I've figured out that running build.cmd is usually a good place to start, but then what? Can I still open the .sln in Visual Studio and build/debug it there?

If you use Sequalize, TypeORM or for MongoDB, we have Mongoose these types of ORM tools, then you are safe by default because these help us against the SQL query injection attacks by default.

We decided to use MySQL for a database. and TypeOrm for ORM. The ER diagram is provided below. For example, the task_assignments table holds information about user assignments to tasks. While in DDD, there is a pattern to design denormalized tables that reflect the structure of domain objects more directly, but this time, a more conventional table design was chosen. TypeOrm models:

How does this compare to using directly an ORM lib that supports browser like TypeORM [0] via SQL.js [1]?

[0] https://typeorm.io/

* Patch a third-party library that was setting an HTTP header to `null`. NodeJS handles this case just fine, but Deno throws an error [2].

After all of that work, I finally was able to use Deno in my project. It was really cool! Unfortunately, both VS Code and IntelliJ with Deno are essentially unusable [3]. Or, at least, unacceptably slow compared to what I had with NodeJS.

[0]: https://stackoverflow.com/a/66073607

[1]: https://github.com/typeorm/typeorm/issues/6123#issuecomment-...

[2]: https://github.com/Sansossio/twisted/issues/97

[3]: https://github.com/denoland/vscode_deno/issues/895

TypeORM is a very convenient ORM for JS apps. We use it with NestJS and running it on NodeJS.

We are going to start using TypeORM as an ORM to help us interact with Postgres, but we also have an example of using Prisma in the future and everything that we have to adapt to switch the ORMs if necessary. At the end we are implementing neon.tech as a production database, right? 😉

TypeORM is a popular Object-Relational Mapping (ORM) library for Node.js. It provides a high-level abstraction over relational databases, making it easy to perform CRUD (Create, Read, Update, Delete) operations.

TypeORM places its focus on TypeScript and JavaScript (ES7+) development. It offers compatibility with various database systems, including MySQL, PostgreSQL, SQLite, and MongoDB. What sets TypeORM apart is its robust integration with TypeScript. It provides a user-friendly experience with a convenient decorator-based syntax for defining entities and relationships. Additionally, TypeORM supports the repository pattern and enables eager loading, enhancing its versatility for developers.

ᴬ typeorm officially supports mssql@v9, but the support for the custom stream builder was added in mssql@v10. Since mssql is a peer dependency of typeorm, you can force override it and use the Cloud SQL Connector with typeorm. There is an open PR to add support for mssql@v10 in typeorm.