I Have A New Favorite Database Tool 

I think a lot of your audience already starred Drizzle weeks or months ago to be honest

Drizzle is fast and se-x-y

@t3dotgg I have learned a lot from you Theo; especially from the t3 tutorial video. Any chance you could post a video showing how you'd refactor the Prisma part of the Chirp T3 Tutorial app to Drizzle?

You want people to go and blindly star something they have no experience with?

This is exactly why Drizzle exists - so that you can learn SQL instead of learning an ORM.

yeh, orms having query syntac similar to sql are the best, Learn once and use everywhere

Lol

What's an ORM. SQL pg all the war

This was the main reason I gave up on TypeORM. Even the simplest queries did some back-and-forth, which is fine for the old days where the DB was hosted on the same machine as the application, but when your DB is on AWS or some cloud provider, as is the current trend, you really start to notice that extra latency.

@@gosnooky but in general why would you have it in different locations ? Maybe I don’t get it but aren’t you supposed to always have your server “close” to your db ?

@@ajnart_ Serverless. Your DB isn't going to be deployed on your lambda.

You can do it with drizzle! We have custom types to do any kind of post-processing

@@andrewsherman4610 Thank you! Trying to do this now with an arrayFromPSV type and apparently I can't return a string array from toDriver (as I would have to when converting a pipe-separated or comma-separated string to an array) and the only type I can return is a string? Is there a way around this? Thanks in advance! code: const arrayFromPSV = (psv: string) => customType({ dataType() { return 'string[]'; }, toDriver(value: string): string[] { return value.split('|'); }, })(psv); export { arrayFromPSV } Error: type '(value: string) => string[]' is not assignable to type '(value: string) => string | SQL'. Type 'string[]' is not assignable to type 'string | SQL'.ts(2322) index.d.ts(300, 5): The expected type comes from property 'toDriver' which is declared here on type 'CustomTypeParams'

changing the type for driverData to string[] made the type error go away, now let's see if it actually works in implementation...

​@@owenwexler7214 Update? :)

I don't see it changing for the next 6 months, but maybe he'll announce it for 2024

it happen

This vid was part of an earlier livestream, so theo isn't THAT influential lol

😭

Stephen*

Hi

Feel free to reach out to drizzle team and explain what was not working for you! Would love to assist you with any problems you had

Not sure it's still even maintained these days and, anyway, I prefer the column declaration in one line

All of the T3 deps are still great! Don't mistake my excitement for new tech as disdain for previous recommendations. I still ship Prisma, NextAuth, tRPC and Page Dir every day That said...there may be a repo floating around on my github profile...🤐

Would be awesome to see a video about that repo 😁

MariaDB is breddy gud. There's also Oracle and MS if you're not the one paying. But if you are, why are you using either of those?

They all suck if you don't understand them well and all you know is SELECT * FROM blah WHERE ala='something'. And that's like 95% of so called "engineers" nowadays

​@@IvanRandomDude I mean, if you're not a backend or ops guy, you have that excuse, but I do agree. I probably set the bar for okay lower than most though.

Yes, most real database tools are meant to be run on servers.

Nice meme

We can add react native driver, no problems

That is the main reason why I switched to drizzle, honestly. Having to manually update every schema of an endpoint after a migration really is a dealbreaker for me

@@lucas.p.f prisma has that too

​@@thecarpenter_son it does? How? And where?

@@thecarpenter_son yeah, there are some out there but they aren't nearly as good as drizzle-zod. prisma-zod-generator, for an example, generates a lot of garbage code that will stick with you and every change requires you to run a script to regenerate all the files. With drizzle, I change a line of code and there you go. Everything that depends on it just changes altogether.

So they have a built-in Joi? Am I reading this right?

You're probably not familiar with type safety in typescript, and the many additional benefits it provides

@@ziad_jkhan I've spent years with C, C#, Java, several ORMs, and am a big proponent of OOP, so I'm pretty comfortable with types. In the end, one gets tired of chasing the next new shiny thing and the best policy becomes sticking to standards that last.

@@netssrmrz Typescript standards will last as long as JS does and the Drizzle syntax is based on the sql syntax so it'll last as well. Anyway, if you want standards that last then the world of programming is probably not the best place to be for you.

DataGrip if your org has jetbrains is very nice to use even if kinda bloat.

Building this right now! alpha.seltzer.dev

@@_heyglassy Hmm is there more info?

Isn’t Prisma studio is literally just db viewer ? Dbeaver can do that for more than a decade now

react native is also not at version 1 ...

Objection is awesome and my usual pick. Can you explain why drizzle is better and in what way?

@@PerpetualWarr Objection is amazing but it falls short when trying to support TypeScript. They do an ok job but because they started with JS, some design decisions were made to makes it hard to support TS, so it takes a lot longer to adopt new features. Also, the main author of Objection did a post 6 months ago saying it's essentially going to get sunset and he's working on Kysely now, so updates will be few and far between. With Drizzle, everything is TS-native (as in they don't even try to support other languages like Prisma does). Because of this, they can adopt new features much faster and they can also take advantage of TS features like decorators to make the API much nicer to use, and I think Prisma doesn't do that. They're also a lot easier to use via other schema-based ORMs. I think with this latest update where Drizzle will make exactly one call to the DB will actually beat out Prisma in a lot of cases in terms of performance, although I'll have to benchmark to confirm. All in all, I like the direction the project is headed and a lot of big tech personalities are starting to back it (check the sponsers)

TypeORM is the best, you can customize it like you want

disclaimer: idk if RU-vid uses firebase

Fo shizzle

I adapted this tool based on RU-vidrs praising it over Prisma, and I’m seeing issues on a fundamental level. Like it’s not able to insert booleans correctly, and it doesn’t set default values for fields even though specified that it should in its schema. Heck its introspection tool generates types with syntax errors at times. Drizzle doesn’t have a 1.0 release yet, and any upgrade can include drastic changes that can break functionality. While it’s true it has great performance, but what good is that if the result you’re getting is incorrect? You can mitigate performance but correctness…yikes! I have to go back to rethink what ORM to use.

From an artistic perspective may be you're right but there are many benefits of using pure TS for that like extensibility and less dependencies

DRY too. If it's defined in the code that is using it then you'r going to be repeating, surely? Which is a maintenance no no.

this shit is bugged as fuck, its impossible to code with typescript, its full of any everywhere is the code at least with prisma you got correct type

Asking people to star something they have not even tried does not sound right to me