On Wed 13 Dec 2023 at 00:03:57 (+0700), Max Nikulin wrote:
> On 08/12/2023 11:38, to...@tuxteam.de wrote:
> > On Thu, Dec 07, 2023 at 10:18:44PM -0600, Nicholas Geovanis wrote:
> >
> > > All of these considerations are what brought Oracle to create a
> > > proprietary
> > > "datetime" datatype an
On 08/12/2023 11:38, to...@tuxteam.de wrote:
On Thu, Dec 07, 2023 at 10:18:44PM -0600, Nicholas Geovanis wrote:
All of these considerations are what brought Oracle to create a proprietary
"datetime" datatype and use it to store all "real" dates/times. If you need
a different format for display
On Thu, Dec 07, 2023 at 10:18:44PM -0600, Nicholas Geovanis wrote:
[...]
> All of these considerations are what brought Oracle to create a proprietary
> "datetime" datatype and use it to store all "real" dates/times. If you need
> a different format for display purposes or a human readable column
On Fri, Dec 08, 2023 at 09:11:12AM +0700, Max Nikulin wrote:
> On 07/12/2023 23:08, tomas wrote:
> > On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> > > On 07/12/2023 21:22, John Hasler wrote:
> > > > Databases should never store local time.
> > >
> > > There are exceptions when sto
On Thu, Dec 7, 2023, 8:11 PM Max Nikulin wrote:
> On 07/12/2023 23:08, tomas wrote:
> > On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> >> On 07/12/2023 21:22, John Hasler wrote:
> >>> Databases should never store local time.
> >>
> >> There are exceptions when storing UTC instead
On 07/12/2023 23:08, tomas wrote:
On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
On 07/12/2023 21:22, John Hasler wrote:
Databases should never store local time.
There are exceptions when storing UTC instead of local time leads to
undesired consequences.
Heh. There was one hug
On Thu, Dec 07, 2023 at 10:29:29PM +0700, Max Nikulin wrote:
> On 07/12/2023 21:22, John Hasler wrote:
> > Databases should never store local time.
>
> I am anticipating a new branch of hot discussion.
>
> There are exceptions when storing UTC instead of local time leads to
> undesired consequenc
On 07/12/2023 21:22, John Hasler wrote:
Databases should never store local time.
I am anticipating a new branch of hot discussion.
There are exceptions when storing UTC instead of local time leads to
undesired consequences.
Planned (future) events may be bound namely to local time. So if
t
8 matches
Mail list logo