Most stuff should be in the documentation. Maybe I’ll add a paragraph about configuring the timezone db as well at a later time. I’d also gladly accepts questions/improvements on that part.
LostKobrakai
azimlord
Hey I’m building an API for the same function,
but when passing the input_start_time: 2019-09-20T10:00 and input_end_time: 2019-09-20T11:00 it returns an error
(ArgumentError) argument error
:erlang.binary_to_atom(nil, :utf8)
(tzdata) lib/tzdata/release_reader.ex:91: Tzdata.ReleaseReader.do_periods_for_zone_time_and_type/3
(tzdata) lib/tzdata/release_reader.ex:72: Tzdata.ReleaseReader.periods_for_zone_time_and_type/3
(tzdata) lib/tzdata.ex:242: Tzdata.possible_periods_for_zone_and_time/3
(tzdata) lib/tzdata.ex:196: Tzdata.periods_for_time/3
(tzdata) lib/tzdata/time_zone_database.ex:32: Tzdata.TimeZoneDatabase.time_zone_periods_from_wall_datetime/2
(elixir) lib/calendar/datetime.ex:262: DateTime.from_naive/3
(tz_datetime) lib/tz_datetime.ex:190: TzDatetime.do_handle_datetime/3
Do you know what am I missing?
0
Nicd
You have to show your code. It seems like you are passing a nil somewhere where a binary is expected.
0
LostKobrakai
Seems like a problem of tzdata. Did you update the library to the most recent version? Afaik every now and the there are problems with changes in the data format of the file it‘s consuming.
0
azimlord
schema "booking" do
field :reference, :string
field :status, :string
field :start_time, :utc_datetime
field :end_time, :utc_datetime
field :time_zone, :string
field :original_offset, :integer
field :input_start_time, :naive_datetime, virtual: true
field :input_end_time, :naive_datetime, virtual: true
timestamps()
end
def create_changeset(booking, attrs) do
booking
|> cast(attrs, [:reference, :status, :start_time, :end_time, :time_zone, :original_offset, :input_start_time, :input_end_time])
|> validate_required([:input_start_time, :input_end_time])
|> change_start_end_timezone()
end
defp change_start_end_timezone(changeset) do
changeset
|> TzDatetime.handle_datetime(input_datetime: :input_start_time, datetime: :start_time)
|> TzDatetime.handle_datetime(input_datetime: :input_end_time, datetime: :end_time)
end
Create function
def create(conn, %{"booking" => params}) do
with {:ok, %Booking{} = booking} <- MyContext.create_booking(params) do
render(conn, "show.json", booking: booking)
end
end
def create_booking(attrs \\ %{}) do
%Booking{}
|> Booking.create_changeset(attrs)
|> Repo.insert()
end
My request
{
"booking": {
"input_start_time": "2019-09-20T10:00",
"input_end_time": "2019-09-20T11:00"
}
}
here you go
0
azimlord
Yup. I check the code in GitHub, but I don’t really understand it.
I’m using the latest version for both tz_datetime and tzdata
[
{:tz_datetime, "~> 0.1.1"},
{:tzdata, "~> 1.0.1"}
]
I did not update tzdata but I tried both version 0.1.0 and 0.1.1 of your library
It worked on web, it just does not work for API
0
Nicd
azimlord
Thank you for telling me that. The time_zone need to be set.
My request should be like this
{
"booking": {
"input_start_time": "2019-09-20T10:00",
"input_end_time": "2019-09-20T11:00",
"time_zone": "Asia/Kuala_Lumpur"
}
}
I forgot that I need to manually set the time_zone for tz_datetime and tzdata to work.
It is actually in the past conversation from this thread. My bad 
Thank you very much!
0
azimlord
Question
Since the start_time is stored as UTC. How would you suggest to do query by date or datetime. For example:
date = "2019-09-20" #Let's say this date is from "Asia/Kuala_Lumpur"
date = Date.from_iso8601!(date)
Booking
|> where([b], fragment("?::date", b.start_time) == ^date)
|> Repo.all
The results would be wrong, where it tries to compare date from a different time zone
0
LostKobrakai
Comparing datetimes should generally happen with UTC values only. The problem of dates is that a date doesn‘t have a timezone. If you want to match a date in asia to a utc datetime you‘d need to convert it first to the appropriate datetime interval in UTC matching the start/end datetimes for the given date in your timezone.
0