Thank you very much for your explanation!
¡° Include¡m"Stephan Szabo" <[EMAIL PROTECTED]>¡n
wrote:
>There have been discussions in the past about when cascade
events
>should occur. The code currently does what I believe was
last
>agreed upon, although its behavior is fairly wierd for
deferred
Hi!
It looks to me a referential integrity problem (only?)
within PLPGSQL. Plesase see the test result below.
Thank you!
CN
===
CREATE TABLE test1(c1 INTEGER PRIMARY KEY) WITHOUT OIDS;
CREATE TABLE test2
( c1 INTEGER,
c2 INTEGER,
PRIMARY KEY (c1,c2),
CONSTRAINT ctest2 FOREIGN KEY (c1)
¡° Include¡m"Tom Lane" <[EMAIL PROTECTED]>¡nwrote:
>> So, what is the official syntax?
>
>See the SET command's reference page. I believe you need
to quote
>anything that doesn't look like an identifier or number.
Thank you very much! You have clarified all my timestamp and
time zone questions
Thank you! Tom,
>The documentation does not actually say any such thing,
although its
>failure to clarify what it *is* saying isn't great. I have
reworded it
>as follows in CVS tip:
>
>: Table B-4 shows the time zone abbreviations recognized by
PostgreSQL in
>: date/time input values. PostgreS
Hi!
Seeing no comments on the same issue I raised in
pgsql-general list, I am posting it here.
The documentation (Appendix B.2. Date/Time Key Words) says
that the following SQL's are legal, but actually they are
not:
SET TIME ZONE TO ''
(examples:
SET TIMEZONE TO 'NZDT';
SET TIMEZONE TO 'EST';
Hi!
pgsql 7.2, Linux 2.0.35.
procedure to reproduce incorrect result:
(1)
either
initdb -E EUC_TW
or
initdb -E MULE_INTERNAL
(2)createdb database1
(3) psql database1
(4) create table test (f1 charchar(255) primary key);
(5) insert into test values('¦¨¥\');
(6) insert into test values('³\');
E
