2 different 'time' query results between staging and production?

Wappler General Need Help
1

Hey All,

Just a general question here as to why i might be getting two different results from a certain time field returning from a postures query between by staging and production environment?

Staging is returning:
end_time: "17:00:00"

and Production is returning:
end_time: "17:00:00.000Z"

In the database, the time reads “17:00:00” and this is what should be displayed. Adding the timezone element at the end stops it from being displayed/recognized in the input filed in the front end

They are the exact same DB fields, same datatype (Time, 6 characters), same query same everything…

But for some reason, the production query is adding the timezone element.

Any ideas?

Naturally i can add some formatting in the query…but this shouldn’t be happening anyway :slight_smile:

2

Same database software version?

3

good question…i’ll check

4

Yes same version. They are in face both running on the same Manage DB server/account on Linode, just separate databases

5
  1. Same version of the Wappler app deployed on staging and production?
  2. Same version of NodeJS deployed on staging and production?
  3. Confirm using a third-party DB viewer the schema, if it’s really the same one

And then I don’t have any further ideas :slight_smile:

1 Like
6

appreciate the responses…i’ve changed the query for now using to_char() , but still want to get to the bottom of it

7

Ok…turns out that somehow my product environment was on UTC time for the new Timezone Handling feature of the DB connections and all my dev and staging environments are on Driver Dependant as they should be.

A bit strange how this changed in the latest update but only the environment…will need to keep a close eye on that.

But changing it back to Driver Dependent fixed this issue

1 Like