TypeScript
final not = DateTime.now();
print(not.timeZoneName);
print(not.toIso8601String());
print(not.toLocal().toIso8601String());
so when we actually add a value in DateTime object in apwrite we actually converting the DateTime into ISO string. In my case, my timezone is philippines, but when adding it to appwrite it converts into a UTC timezone?
TL;DR
The user is asking how to handle timezones correctly when using the DateTime object in Appwrite. The solution is to send the DateTime object to Appwrite in UTC format by using the toUTC() function instead of toLocal().You should be sending it to Appwrite in UTC. So do toUTC() instead of toLocal()
Recommended threads
- Appwrite console is too heavy
The Appwrite console is too heavy And all of my services broken Any support , please
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...
- Increase by operators
I see appwrite have bunch of useful operators for querieng db. One more I would like to suggest is operators like increase the count of a int columns by 1,2.. ...