Object–relational mapping

When I saw the headline for the survey, I thought, oh, it's going to survey Django things.

Like who's using this feature, the ORM, and then who's deploying this way versus that way.

And no, it's more of a general thing.

Just let's ask the Django people what they're up to.

In fact, even this morning, Stefan was like, I think I've figured out a good way to do this where we'll get really resilient retries, but we can't use EF Core.

I was like, well, why did we use EF Core to begin with? Going back nearly 13 years, I was just EF then, we used EF because an ORM saved us a lot of overhead writing code.

But now we have Copilot.

So do we just go, hey, Copilot, replace everything that's in EF Core with native SQL client and whatever retry or resiliency model that Stefan's built? So I think we can probably just do that and it will make life a lot easier.

In other cases, you know, again, we already talked about performance potential issues here that there may be other tools that could potentially speed it up or whatever.

I just remember somebody recently saying, well, I had it just write Instead of having an object relational mapper, an ORM kind of system, I had it just write the core SQL stuff and so forth.

And it had a bit of a performance boost, but at the end of the day, he was still having a hard time understanding the code out of it.

So there's going to be a balance there.

And, you know, we have to do the code reviews and everything.

we have that ultimate responsibility if something breaks, we're the ones who have to fix it.

And if it's just bytecode or if it's the low-level SQL that we just can't follow without having that ORM wrapper on top, then it's going to be a struggle.

Yeah, so, you know, my experience is it's good to have some layers in there.

And then you need something that talks to it.

The ORM.

Django's ORM in this case.

This is the part where most front end developers have seen the syntax but haven't seen what it actually does.

You write item.objects.filter, and you get back what looks like results.

It's not results.

A query set is a specification of a query that hasn't run yet.

The ORM is aggressively lazy.

Alright, so let's dive into interaction here.

We're rocking two Sword Supply Shares and four Force of Wills, and I guess you can consider an Orm's Chant as interaction to some extent.

Talk to me a little bit about this particular suite of interaction.

Yeah, well, the four Force of Wills are easy.

You're never going to play, like, Povtex on this deck over Souls of Plowshares, if I put it that way.

Yeah.

Alright, well, let's talk a little bit more about Orm's Chant, and why this is in the deck, as opposed to, say, something like Teferi

Timerap.

And that's actually the perfect way to look at the first step of our framework, which is absorption, the A in ADME.

ORM.

Yeah.

Absorption is the physical movement of the drug from wherever it entered your body into the systemic circulatory system.

Writing financial data in plaintext on a mobile device is an architectural failure.

Reactive state and ORM, the core state management relies on for surgical UI rebuilds.

For relational persistence, I use Drift, a reactive worm built on top of SQLite.

Military-grade disk encryption.

Yeah.

And it's the heavy hitters, models, which is sort of our ORM by proxy, admin, auth.

Yeah.

There's a long tail-

And all the rest, yeah.

[chuckles]

I mean, you know, I think most people if pushed to shove would say the ORM or the admin, that has to be in the top three, five-

Yeah