On Thu, Feb 06, 2003 at 05:25:39PM +1300, Rodger Donaldson wrote:
> On Wed, Feb 05, 2003 at 11:22:57PM -0500, Tom Lane wrote:
> > Rodger Donaldson <[EMAIL PROTECTED]> writes:
> > > values(to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/:HH24:MI:SS'),0,302,
> >
> > > Always inserts the correct
On Wed, Feb 05, 2003 at 11:22:57PM -0500, Tom Lane wrote:
> Rodger Donaldson <[EMAIL PROTECTED]> writes:
> > values (to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/:HH24:MI:SS'),0,302,
>
> > Always inserts the correct date, but sets the time to midnight.
>
> Um, well, yeah ... it's to_DATE,
Rodger Donaldson <[EMAIL PROTECTED]> writes:
> values(to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/:HH24:MI:SS'),0,302,
> Always inserts the correct date, but sets the time to midnight.
Um, well, yeah ... it's to_DATE, meaning it produces a result of type
date. I think you wanted to_t
Postgresql 7.2.3
insert
intolog_entries
values (to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/:HH24:MI:SS'),0,302,
[... various other data elided ...]);
Always inserts the correct date, but sets the time to midnight.
Thinking this might be solved by shuffling with the source d
