| 8 Jan 2024 |
 cofin | this ensures you always store as UTC | 19:58:29 |
 pedro.diaz | thanks, I found it. I was looking for this one
connect_args={"server_settings": {"TimeZone": "America/Caracas"}}
| 20:06:39 |
| pedro.diaz | This one works for asyncpg | 20:06:43 |
| cofin | I'll have to remember this one | 20:07:02 |
| pedro.diaz | https://stackoverflow.com/questions/26105730/sqlalchemy-converting-utc-datetime-to-local-time-before-saving
https://github.com/MagicStack/asyncpg/discussions/893 | 20:07:38 |
| pedro.diaz | My references | 20:07:40 |
 .jurajura | 
Download image.png | 20:40:03 |
| .jurajura | Hey, first wanted to give a quick shoutout to whoever wrote the docs since they've been absolutely great to go through!
Two small nitpicks I noticed:
1. https://docs.litestar.dev/latest/tutorials/sqlalchemy/4-final-touches-and-recap.html The very last code snipped of this tutorial page seems weird. Wrong offset or smth?
2. Available issues directs to the github repositories page instead | 20:40:04 |
| .jurajura | Sorry, I'd create a PR myself but I'm on far too many sidequests to go on this one today. Hopefully will contribute one day though :) | 20:40:36 |
| pedro.diaz | ππ
| 20:40:53 |
| cofin | Thanks. I'm actually working to update the SQLAlchemy docs to include services and alembic. I'll work this in | 20:41:26 |
| pedro.diaz | yeah some things in the docs are wrong/outdated | 20:41:39 |
| pedro.diaz | there's something in the jwt part of the docs | 20:41:51 |
| pedro.diaz | I just remembered that I have to create a pr to fix that part | 20:42:02 |
| pedro.diaz | I hope no one finds out | 20:42:15 |
| pedro.diaz | π | 20:42:40 |
| pedro.diaz | π | 20:43:07 |
| .jurajura | Well out of all ASGI framework documentations I've read recently this one stands out as the best for sure. Big selling point for me, for sure :) | 20:55:16 |
| 9 Jan 2024 |
|  francbartoli joined the room. | 19:10:55 |
| 10 Jan 2024 |
 awstam | and this community rocks | 10:55:10 |
|  aldeguer_92622 joined the room. | 14:41:03 |
|  alva_814 joined the room. | 16:30:41 |
|  blockjoe joined the room. | 18:55:04 |
|  hasebali joined the room. | 19:07:53 |
 kumzy | @Kumzy you may be interested in this PR | 19:15:03 |
 pltoledo | Hi guys! I just recently got to know litestar, and I got say I really like the product so far!
I am thinking about adopting litestar in one of our products, but I wanted to know what are the plans for litestar long-term? | 22:45:09 |
 minhphuong0401 | Hi guys. Just started with litestar and love it. Just want to check if itβs possible to have different response type based on parameters. For example @get /vehicle/{param:str}. If param=BMW, return list[BMWcar]. If param=VW, return list[VWcar] | 22:51:50 |
|  lmo_23 joined the room. | 23:09:28 |
| cofin | Glad you are checking us out!
We want Litestar to be around for years to come, so right now, our plans are focused on squashing bugs and cleaning up a bit of technical debt from the fast paced development leading into 2.0.
We'll begin shifting our focus into a stable 3.0 release this year, and we want this transition to be much smoother than the jump from 1 -> 2.0.
We've talked in depth on this in several of our office hours (you can reference the recordings in discord), but we are admittedly overdue in writing this down.
Is there anything in particular you'd like to know? | 23:22:22 |
|  DarkJedi5400 joined the room. | 23:47:27 |
