Hi to all,
I have a problem storing 1973/06/03 date.
If I send this statement
select to_date('03/06/1973','dd/mm/');
in the psql interface I obtain
to_date
1973-06-02
I test this statement with Postgres 7.3.2 and 7.3.4 packaged withMandrake 9.1
and Mandrake 9.2RC1 and
On my 7.4 this select works fine
testdb011=> select to_date('03/06/1973','dd/mm/');
to_date
1973-06-03
Pavel
On Wed, 10 Sep 2003, Torello Querci wrote:
> Hi to all,
>
> I have a problem storing 1973/06/03 date.
>
> If I send this statement
>
> select to_date('03/06/
On Wed, Sep 10, 2003 at 12:52:22PM +0200, Torello Querci wrote:
> Hi to all,
>
> I have a problem storing 1973/06/03 date.
>
> If I send this statement
>
> select to_date('03/06/1973','dd/mm/');
>
> in the psql interface I obtain
>
> to_date
>
> 1973-06-02
>
> I test t
POSTGRESQL BUG REPORT TEMPLATE
Your name : Christoph Jäger
Your email address : christoph.jaeger ( at ) dhl
Am Mittwoch, 10. September 2003 12:52 schrieb Torello Querci:
> Hi to all,
>
> I have a problem storing 1973/06/03 date.
>
> If I send this statement
>
> select to_date('03/06/1973','dd/mm/');
>
> in the psql interface I obtain
>
> to_date
>
> 1973-06-02
>
> I test this state
Torello Querci <[EMAIL PROTECTED]> writes:
> If I send this statement
> select to_date('03/06/1973','dd/mm/');
> in the psql interface I obtain
> to_date
>
> 1973-06-02
What timezone are you in? What do you get from
select to_timestamp('03/06/1973','dd/mm/');
Tom,
I got a reply back from someone on the apple
developers list.
> gcc -traditional-cpp -g -O2 -Wall
-Wmissing-prototypes
^^^
This is wrong. You need to use -no-cpp-precomp. It
says this in the release notes for the December tools
updater, as well as a number of other thin
"Christoph Jaeger" <[EMAIL PROTECTED]> writes:
> PostgreSQL version (example: PostgreSQL-7.3.4): postgresql 7.1.3
7.1.3 is ancient history, and no it doesn't have defenses against you
changing a column definition that a foreign key linkage refers to.
I'd recommend updating to 7.3.4.
> The tab
I think this is what you wanted.
select to_char('03/06/1973'::date,'dd/mm/');
you were casting the string to a date and returning a
date. so it would return it in a format that your
system is set to return.
agencysacks=# select
to_char('03/06/1973'::date,'dd/mm/');
to_char
If anyone is interested, the only solution I have
found is not use it. I refer to the december 2002
update to OS X developers tools which includes the gcc
3.3 compiler.
the solution if you have installed it is to set your
mac back to 3.1.
su
gcc_select 3.1
su postgres
./configure (with what y
This is not a bug, but simply due to postgres date formatting. Observe
thus:
gbi=# set datestyle to 'iso';
SET
gbi=# select to_date('03/06/1973','dd/mm/');
to_date
1973-06-03
(1 row)
gbi=# set datestyle to 'us';
SET
gbi=# select to_date('03/06/1973','dd/mm/');
to_
Jord Tanner <[EMAIL PROTECTED]> writes:
> This is not a bug, but simply due to postgres date formatting.
Yes, it's a bug, but it's specific to the Europe/Rome timezone setting.
I've not yet had a chance to figure out the details.
regards, tom lane
12 matches
Mail list logo
