Yeah, I was wondering what this custom db connection of 0.23 would allow. Thanks for your attempt to explain the benefits, but I think more videos with further explanations are needed
Glad I could help. There is going to be many more video's as I find more use cases - I think the biggest one I am looking at is Pocketbase as a vector DB and Pocketbase + GEOJSON which now appears to be a possibility
Looks like the Pocketbase owner is getting a bit overwhelmed by the community’s requests! 😅 I guess everyone just wants their app to run perfectly, but a little patience goes a long way! Hang in there, we all appreciate the hard work! 🙌
Hi! Liked the rounded brests! I also dont really understand what is the point of pocketbase here ? Why dont just just create a turso db and then use the turso sdk via your front end app?
They are good aren't they! Yeah I think it's just a case of being able to get the hooks and auth of Pokcetbase while getting the benefits of Turso up time and syntax simplicity with SQL. For me and my projects this doesn't make a difference as if I need sql I will just use a custom hook function. But I know this addresses peoples requests for this feature and it also opens the realm of offline first pocketbase and also vector dB's within pocketbase
@@earlymorningdev not sure I understand how does libsql help with offline first case, what did you mean? The biggest benefit I see in turso is easy db per user pattern which as far as I understand won’t work with pocketbase, so we’re left with read replicas, backup, and vector search; which is still great vs litestream
Well if you hook up sqllite cr you can sort of get offline first. I am still looking into how to do it but my point was there are a lot of options now for working with all sorts of data we couldn't before. Like there is sqllite geo libs as well which is awesome for some of my projects
@@earlymorningdevCan you please link to the user requests you're referencing here? As you say, you can already use raw SQL via a PocketBase hook. Any db writes done outside of PocketBases's Model/Record API will bypass all PocketBase security and events and should be done with extreme caution.
It would be cool to see if people build a library that infers your pocketbase collections and builds the correct ORM for it. So I have all the typed queries i need based on my collections.
At 25:04 you show accessing Turso from the Turso web client. I would advise caution as this is making a database access key public. Anyone can obtain the key and use it to query the database directly, bypassing PocketBase's robust security entirely.
May I ask? What for do you want to do that? This will slow down your response time and make you pay a larger bill... I remember we had something for regular backups. Also how about encryption and authed users?
Good considerations. How exactly will it slow response time? Yeah encryption and authentication is something I still have to explore. Will probably do a follow-up to this one
@@earlymorningdev Eh (if you're not going to use turso directly, which you probably won't because of auth verification)... you'll have to go to your pocketbase instance first and pb will req a res to send you back that response.
I think this is step forward but the DX is not as good as PB. Maybe in the future the integration can be done through a cli or something when setting up pb instead of having to do all the custom go code since maybe PB user probably to work a lot with go compared to JS. Does this mean you have to reimplement API rules on top of turso to get what you currently get from PB for free ?
Yeah, I was wondering what this custom db connection of 0.23 would allow. Thanks for your attempt to explain the benefits, but I think more videos with further explanations are needed
Glad I could help. There is going to be many more video's as I find more use cases - I think the biggest one I am looking at is Pocketbase as a vector DB and Pocketbase + GEOJSON which now appears to be a possibility
Pocketbase has been, by far, one of my favorite Go projects. I use it as a framework for many projects. Seeing Turso as an option is bloody fantastic.
Yeah it's flipping awesome. There are so many options for scaling now
you seems to fan of pocketbase nice work
Of course it is the best 👌
Turso with pocketbase is just amazing!
Looks like the Pocketbase owner is getting a bit overwhelmed by the community’s requests! 😅 I guess everyone just wants their app to run perfectly, but a little patience goes a long way! Hang in there, we all appreciate the hard work! 🙌
base on the way he respond (i respect his work)
Yeah Gani is doing a great job. This change in particular is going to be huge for building better SQL Lite integrations with PocketBase
Hi! Liked the rounded brests!
I also dont really understand what is the point of pocketbase here ?
Why dont just just create a turso db and then use the turso sdk via your front end app?
They are good aren't they!
Yeah I think it's just a case of being able to get the hooks and auth of Pokcetbase while getting the benefits of Turso up time and syntax simplicity with SQL.
For me and my projects this doesn't make a difference as if I need sql I will just use a custom hook function. But I know this addresses peoples requests for this feature and it also opens the realm of offline first pocketbase and also vector dB's within pocketbase
@@earlymorningdev not sure I understand how does libsql help with offline first case, what did you mean?
The biggest benefit I see in turso is easy db per user pattern which as far as I understand won’t work with pocketbase, so we’re left with read replicas, backup, and vector search; which is still great vs litestream
Well if you hook up sqllite cr you can sort of get offline first. I am still looking into how to do it but my point was there are a lot of options now for working with all sorts of data we couldn't before. Like there is sqllite geo libs as well which is awesome for some of my projects
Never heard of cr-sqlite before, looks interesting, thanks!
@@earlymorningdevCan you please link to the user requests you're referencing here? As you say, you can already use raw SQL via a PocketBase hook. Any db writes done outside of PocketBases's Model/Record API will bypass all PocketBase security and events and should be done with extreme caution.
Great video!! Is there a way to use pocketbase with PostgreSQL?
There is a fork that I know of but it really shouldn't be used. For now libsql is all there is
It would be cool to see if people build a library that infers your pocketbase collections and builds the correct ORM for it. So I have all the typed queries i need based on my collections.
I think that would be awesome 👌
At 25:04 you show accessing Turso from the Turso web client. I would advise caution as this is making a database access key public. Anyone can obtain the key and use it to query the database directly, bypassing PocketBase's robust security entirely.
Good point Ben! I think a certain degree of caution is required with this
May I ask? What for do you want to do that? This will slow down your response time and make you pay a larger bill... I remember we had something for regular backups. Also how about encryption and authed users?
Good considerations. How exactly will it slow response time? Yeah encryption and authentication is something I still have to explore. Will probably do a follow-up to this one
@@earlymorningdev Eh (if you're not going to use turso directly, which you probably won't because of auth verification)... you'll have to go to your pocketbase instance first and pb will req a res to send you back that response.
I think this is step forward but the DX is not as good as PB. Maybe in the future the integration can be done through a cli or something when setting up pb instead of having to do all the custom go code since maybe PB user probably to work a lot with go compared to JS. Does this mean you have to reimplement API rules on top of turso to get what you currently get from PB for free ?
That's a good point. I didn't test the api rules for turso
Bro, do another lemonsqeezy vid but with all transaction types
I will soon
hope we can integrate nodejs/deno 2 or bun directly with Pocketbase.
Yep would be good to replace the goja with a real js engine
great news
no no all the city pic should be rounded, unless no one wants to go lol
😅