I don’t understand why this is called a “subset”, while clearly containing new syntax

A subset would be understood by older compilers, this is a superset

Absolutely not a replacement to VBA. Not even close. As usual, Microsoft hypes something everyone wants, and then implements something nobody asked

I timed the transaction and opening of the connection, it takes maybe a 100 milliseconds, absolutely doesn’t explain ghe abysmal performance

Transaction is needed because 2 tables are touched, i don’t want to deal with partially inserted data

Cannot share the code, but it’s python calling .NET through “clr”, and using SqlBulkCopy

What do you suggest i shouldn’t be using that? It’s either a prepared query, with thousands of parameters, or a plain text string with parameters inside (which admittedly, i didn’t try, might be faster lol)

Will try bcp & report back EDIT: I can’t install bcp because it is only distributed with SQLServer itself, and I cannot install it on my corporate laptop.

I will try bcp. Somehow, i was convinced I had to have access to the machine running the sql server to use it, but from the doca i see i can specify a remote host… Will report back! EDIT: I can’t install bcp because it is only distributed with SQLServer itself, and I cannot install it on my corporate laptop.

I would not recommend using parquet instead of csv. Indeed, parquet is a type of wooden flooring, while csv is a human readable file format. As you can see, it is not wise to replace one with the other. Don’t hesitate about asking more questions regarding your home design!

Meh. He s wrong and he knows it. Computer science is definitely about efficient use of computational resources and memory.

React +python + postgres/sqlite

We have a solution

Did they pay every news outlet out there to publish stupid titles? That’s not a fucking apology. Stop pretending

Your last question is equivalent to : why there so many math theories? Can’t we just reuse the old ones?

New language appear as a natural product from research in type theory for ex

Even something as ubiquitous as JSON is not handled in the same way in different databases, same goes for Dates, and UUID. I am not even mentioning migrations scripts. As soon as you start writing raw SQL, I pretty sure you will hit a compatibility issue.

I was specifically talking about python, can’t argue with golang. OK you have a valid point for performance, gotta keep an eye on that. However, I am satisfied for our CRUD api

and how you run your tests? Do you spawn a DB backend for test purposes?

You don’t even mention the 2 main advantages:

• ORM lets you to use plain objects over untyped strings. I take typed anything over untyped anything, everyday
• ORM lets you to use multiple database backends. For ex, you don’t need to spawn a local postgres server, then clean/migrate it after each test suit, you can just use in-memory sqlite for that. OK this has some gotchas, but that’s a massive improvement in productivity