> How can I "binds" PostgreSQL to consider '' as null ?
You can modify src/backend/utils/{datetime,date,timestamp}.c to accept
an empty string as a null value. But imho it is better to fix this in
your input file, perhaps using sed:
sed "s/''/NULL/g" < informix.dump > pg.dump
> I'm using postgres 7.0.2. When I use date_part('day', date) sometimes I
> get wrong values. Ie:
> and date_part('day', '1999-3-28')=27
> and date_part('day', '2000-3-26')=25
> Is it a bug?
It is a problem evaluating day numbers around daylight savings time
transitions. Fixed (I believe) in the
Hello:
I'm using postgres 7.0.2. When I use date_part('day', date) sometimes I
get wrong values. Ie:
and date_part('day', '1999-3-28')=27
and date_part('day', '2000-3-26')=25
Is it a bug?
--
Salvador Mainé
---(end of broadcast)---
TIP 1: subsc
I have a table with a char(20) column called 'name'. This SELECT
returns the proper records:
SELECT * FROM table WHERE name = 'John';
But this one does not return the same records:
SELECT * FROM table WHERE UPPER(name) = 'JOHN';
I believe this is contrary to the SQL standard, which (a
In the current sources, I see:
for (lineoff = FirstOffsetNumber; lineoff <= max; lineoff++)
so it looks like we have this fixed. You can check the 7.1RC1.
>
> If PostgreSQL failed to compile on your computer or you found a bug that
> is likely to be specific to one platform then plea
If PostgreSQL failed to compile on your computer or you found a bug that
is likely to be specific to one platform then please fill out this form
and e-mail it to [EMAIL PROTECTED]
To report any other bug, fill out the form below and e-mail it to
[EMAIL PROTECTED]
If you not only found the probl
Stephan Szabo writes:
>
> Unless I'm horribly misreading the spec, this is correct.
> ORDER BY is used in reference to cursor definitions and
> direct select statements, but is not part of query expressions
> which is what the INSERT INTO references.
>
> ::=
> I
