public inbox for [email protected]
help / color / mirror / Atom feedRe: Convert date and time colums to datetime
6+ messages / 3 participants
[nested] [flat]
* Re: Convert date and time colums to datetime
@ 2025-10-20 02:32 Rob Sargent <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Rob Sargent @ 2025-10-20 02:32 UTC (permalink / raw)
To: Rich Shepard <[email protected]>; +Cc: pgsql-general
> On Oct 19, 2025, at 2:38 PM, Rich Shepard <[email protected]> wrote:
>
> On Sun, 19 Oct 2025, Rob Sargent wrote:
>
>> I think you have to ask why those values were separated in the first
>> place. For instance if they are thought of as a pair in most queries then
>> an alteration might be in order. There can be a large one time cost if
>> these tables occur in a lot of separate sql calls in the business logic.
>
> Rob,
>
> Good point. They're in the contacts table and I use them to determine when
> to make another contact and if prior contacts were more productive in the
> morning or afternoon.
>
> Thanks,
>
> Rich
>
>
Definitely a datetime (single value) problem, imho
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Convert date and time colums to datetime
@ 2025-10-20 12:45 Rich Shepard <[email protected]>
parent: Rob Sargent <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Rich Shepard @ 2025-10-20 12:45 UTC (permalink / raw)
To: pgsql-general
On Sun, 19 Oct 2025, Rob Sargent wrote:
> Definitely a datetime (single value) problem, imho
Rob,
Okay. Now I'm curious: why do you write this?
Thanks,
Rich
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Convert date and time colums to datetime
@ 2025-10-20 12:53 Rob Sargent <[email protected]>
parent: Rich Shepard <[email protected]>
0 siblings, 1 reply; 6+ messages in thread
From: Rob Sargent @ 2025-10-20 12:53 UTC (permalink / raw)
To: Rich Shepard <[email protected]>; +Cc: pgsql-general
> On Oct 20, 2025, at 6:45 AM, Rich Shepard <[email protected]> wrote:
>
> On Sun, 19 Oct 2025, Rob Sargent wrote:
>
>> Definitely a datetime (single value) problem, imho
>
> Rob,
>
> Okay. Now I'm curious: why do you write this?
>
> Thanks,
>
> Rich
>
The way I read your description of how you use these columns currently suggests to me that they could be handled by a single timestamp column. The cost/benefit of converting is another thing altogether.
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Convert date and time colums to datetime
@ 2025-10-20 12:58 Rich Shepard <[email protected]>
parent: Rob Sargent <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Rich Shepard @ 2025-10-20 12:58 UTC (permalink / raw)
To: pgsql-general
On Mon, 20 Oct 2025, Rob Sargent wrote:
>> Okay. Now I'm curious: why do you write this?
> The way I read your description of how you use these columns currently
> suggests to me that they could be handled by a single timestamp column.
> The cost/benefit of converting is another thing altogether.
Rob,
Since either way works I'll save the time cost of converting because my
tables will never be really large.
Thanks,
Rich
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Convert date and time colums to datetime
@ 2025-10-20 13:00 Ron Johnson <[email protected]>
parent: Rich Shepard <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Ron Johnson @ 2025-10-20 13:00 UTC (permalink / raw)
To: pgsql-general
On Mon, Oct 20, 2025 at 8:58 AM Rich Shepard <[email protected]>
wrote:
> On Mon, 20 Oct 2025, Rob Sargent wrote:
>
> >> Okay. Now I'm curious: why do you write this?
>
> > The way I read your description of how you use these columns currently
> > suggests to me that they could be handled by a single timestamp column.
> > The cost/benefit of converting is another thing altogether.
>
> Rob,
>
> Since either way works I'll save the time cost of converting because my
> tables will never be really large.
>
Virtual columns exist: have both!
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Convert date and time colums to datetime
@ 2025-10-20 13:26 Rob Sargent <[email protected]>
parent: Rich Shepard <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Rob Sargent @ 2025-10-20 13:26 UTC (permalink / raw)
To: Rich Shepard <[email protected]>; +Cc: pgsql-general
> On Oct 20, 2025, at 6:58 AM, Rich Shepard <[email protected]> wrote:
>
> On Mon, 20 Oct 2025, Rob Sargent wrote:
>
>>> Okay. Now I'm curious: why do you write this?
>
>> The way I read your description of how you use these columns currently
>> suggests to me that they could be handled by a single timestamp column.
>> The cost/benefit of converting is another thing altogether.
>
> Rob,
>
> Since either way works I'll save the time cost of converting because my
> tables will never be really large.
>
> Thanks,
>
> Rich
>
For sure! Your call
>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-10-20 13:26 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-10-20 02:32 Re: Convert date and time colums to datetime Rob Sargent <[email protected]>
2025-10-20 12:45 ` Rich Shepard <[email protected]>
2025-10-20 12:53 ` Rob Sargent <[email protected]>
2025-10-20 12:58 ` Rich Shepard <[email protected]>
2025-10-20 13:00 ` Ron Johnson <[email protected]>
2025-10-20 13:26 ` Rob Sargent <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox