Where condition doesn't work as expected

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Where condition doesn't work as expected

William Colls
I have the following condition a select statement:

  WHERE "datetime" > '2019-03-31 23:59:59'

datetime is a character field with data in the format YYYY-MM-DD
HH:MM:SS. However it returns any line where the datetime field begins
with 2019. I suspect that I should be using timestamp values, but I
can't figure out how to cast the datetime field value to a timestamp.

Thanks for your time.

William.



Reply | Threaded
Open this post in threaded view
|

RE: Where condition doesn't work as expected

opa6x57




Ken Benson | ken @ infowerks-dot-com

-----Original Message-----
From: William Colls <[hidden email]>
Sent: Saturday, February 8, 2020 2:40 PM
To: [hidden email]
Subject: Where condition doesn't work as expected

>>>>-----Original Message-----
>>>>From: William Colls <[hidden email]>
>>>>Sent: Saturday, February 8, 2020 2:40 PM
>>>>To: [hidden email]
>>>>Subject: Where condition doesn't work as expected
>>>>
>>>>I have the following condition a select statement:
>>>>
>>>>  WHERE "datetime" > '2019-03-31 23:59:59'
>>>>
>>>>datetime is a character field with data in the format YYYY-MM-DD HH:MM:SS. However it returns any line where the datetime field begins with 2019. I suspect that I should be using timestamp values, but I can't figure out how to cast the datetime field value to a timestamp.
>>>>

[Ken.B]  
SELECT to_date('20170103','YYYYMMDD');
https://www.postgresqltutorial.com/postgresql-to_date/


>>>>Thanks for your time.
>>>>
>>>>William.
>>>>
I have the following condition a select statement:

  WHERE "datetime" > '2019-03-31 23:59:59'

datetime is a character field with data in the format YYYY-MM-DD HH:MM:SS. However it returns any line where the datetime field begins with 2019. I suspect that I should be using timestamp values, but I can't figure out how to cast the datetime field value to a timestamp.

[Ken.B]  
SELECT to_date('20170103','YYYYMMDD');
https://www.postgresqltutorial.com/postgresql-to_date/

Thanks for your time.

William.



Reply | Threaded
Open this post in threaded view
|

Re: Where condition doesn't work as expected

Bzzzz
In reply to this post by William Colls
On Sat, 8 Feb 2020 17:39:32 -0500
William Colls <[hidden email]> wrote:

> I have the following condition a select statement:
>
>   WHERE "datetime" > '2019-03-31 23:59:59'
>
> datetime is a character field with data in the format YYYY-MM-DD
> HH:MM:SS. However it returns any line where the datetime field begins
> with 2019. I suspect that I should be using timestamp values, but I
> can't figure out how to cast the datetime field value to a timestamp.

Depending on what you need, use either TIMESTAMP or TIMESTAMPTZ.

[…] WHERE (datetime::TIMESTAMP) > TIMESTAMP'2019-03-31 23:59:59' ;

(note that the TIMESTAMP to the right of the comparison is not
mandatory.)

As it costs, if you have no special reason for the "datetime" column to
dwell in text or varchar, you should consider converting it to a
TIMESTAMP or TIMESTAMPTZ type to avoid any conversion when querying.

Jean-Yves


Reply | Threaded
Open this post in threaded view
|

RE: Where condition doesn't work as expected

Stephen Froehlich
To add some context to Bzzz's statement, read this page:
https://www.postgresql.org/docs/current/datatype-datetime.html

If you were building this table from scratch it should be a timestamp to timestamptz.  ... if you can rebuild the table (CREATE TABLE [new_name] AS SELECT ...) https://www.postgresql.org/docs/current/sql-createtableas.html  you probably should.

- timestamp is for when you know its UTC
- timestamp with time zone / timestamptz can trip you up with environment timezones on the client end, but at the end of the day its more flexible and robust. I always use it because it better matches the R POSIXct data type, which is what I always end up using on the client end. However, be prepared for time zones to drive you a little batty as different clients will default to different time zones for a given connection.

--Stephen

-----Original Message-----
From: Bzzzz <[hidden email]>
Sent: Saturday, February 8, 2020 4:19 PM
To: William Colls <[hidden email]>
Cc: [hidden email]
Subject: Re: Where condition doesn't work as expected

On Sat, 8 Feb 2020 17:39:32 -0500
William Colls <[hidden email]> wrote:

> I have the following condition a select statement:
>
>   WHERE "datetime" > '2019-03-31 23:59:59'
>
> datetime is a character field with data in the format YYYY-MM-DD
> HH:MM:SS. However it returns any line where the datetime field begins
> with 2019. I suspect that I should be using timestamp values, but I
> can't figure out how to cast the datetime field value to a timestamp.

Depending on what you need, use either TIMESTAMP or TIMESTAMPTZ.

[…] WHERE (datetime::TIMESTAMP) > TIMESTAMP'2019-03-31 23:59:59' ;

(note that the TIMESTAMP to the right of the comparison is not
mandatory.)

As it costs, if you have no special reason for the "datetime" column to dwell in text or varchar, you should consider converting it to a TIMESTAMP or TIMESTAMPTZ type to avoid any conversion when querying.

Jean-Yves