Thank you. Is an "exception condition" necessarily an error, or
is a warning also an exception condition ?
A warning/notice is called a "completion condition".
Because other db's only raise a warning. Of course we don't want to
copy that behavior if they are not conformant. See
Zeugswetter Andreas SB writes:
Yes, good. Do we want this in 7.1.0 ? Seems, yes :-(
No way. I'm just giving some food for thought while development is slow.
In any case there seems to be support for the proposed feature. I'm just
waiting for someone to complain that he relies on the
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
to say, it's also not in compliance with SQL.
To quote Tom
Zeugswetter Andreas SB writes:
Thank you. Is an "exception condition" necessarily an error, or
is a warning also an exception condition ?
A warning/notice is called a "completion condition".
Because other db's only raise a warning. Of course we don't want to
copy that behavior if they are
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
to say, it's also not in compliance with SQL.
To quote Tom "paragraph and
Zeugswetter Andreas SB writes:
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
to say, it's also not in compliance with
:AW: [HACKERS] Truncation of char, varchar types
Excessively long values are currently silently truncated when they
are
inserted into char or varchar fields. This makes the entire notion
of
specifying a length limit for these types kind of useless, IMO.
Needless
to say, it's also
Nathan Myers writes:
We have noticed here also that object (e.g. table) names get truncated
in some places and not others. If you create a table with a long name,
PG truncates the name and creates a table with the shorter name; but
if you refer to the table by the same long name, PG reports
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
to say, it's also not in compliance with SQL.
How do people feel about changing
On Mon, Apr 09, 2001 at 09:20:42PM +0200, Peter Eisentraut wrote:
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
to say,
After v7.1 is released ... ?
On Mon, 9 Apr 2001, Peter Eisentraut wrote:
Excessively long values are currently silently truncated when they are
inserted into char or varchar fields. This makes the entire notion of
specifying a length limit for these types kind of useless, IMO. Needless
11 matches
Mail list logo
