Herbert R. Ambos [EMAIL PROTECTED] writes:
[ drops only column of a table ]
Is this allowed in SQL?
The SQL spec forbids that. We deliberately decided to ignore the spec
restriction, because it creates too many unpleasant boundary cases for
tools that want to manipulate table definitions.
Hey guys,
I found this interesting
test=# create table t ( c char);
CREATE TABLE
test =# \d t
Table
public.t
Column |
Type | Modifiers
+--+---
c | character(1) |
test =# alter table t drop column c;
ALTER TABLE
test =# \d t
Table
What is it actually giving you as an error
message in the failing case? Someone pointed
out a problem in deferred constraints recently
and I think this may be related.
Stephan Szabo
[EMAIL PROTECTED]
On Mon, 20 Nov 2000, Kyle wrote:
Here's an interesting test of referential integrity. I'm
Here's an interesting test of referential integrity. I'm not sure
if this is working the way it should or if it is a bug.
I'm trying to update the primary key in records that are linked together
from the two different tables. My initial assumption was that because
of the cascade, I could update
