Hi:

Today I compiled, revision 4457 and still same strange behavior. I
didn't expect any different because SVN mails didn't make references to
this problem. It seems that is a "just me" issue.

Anyway, any hint to discover what I have done wrong ?. I made a fresh
new checkout this time but makes no difference.

Anyone has compiled revision 4457 under Fedora Core 4 with wxWidgets
2.6.1 ?.

Previous posts were on hacker's list.

Regards,
Diego.

El lun, 19-09-2005 a las 16:19 -0300, Diego Gil escribió:
> Hi,
>
> It seems strange to me that nobody else reported this behavior, maybe a
> bug.
>
> It just me or what ?. :-).
>
> Today I compiled revision 4455, with an updated postgresql 8.1 beta 2
> and still can't modify any table due to "ADD before DROP" issue.
>
> It seems to happen only in table properties dialog. I can add or modify
> any table object using ad-hoc property dialogs.
>
> To reproduce it, open a table property dialog and look to SQL tab. It
> should say "-- nothing to change" but in my case shows constraints's add
> code and corresponding constraints's drop code.
>
> Regards,
> Diego.
>
> El vie, 16-09-2005 a las 23:53 -0300, Diego Gil escribió:
> > Hi:
> >
> > I just realized that I am having the following trouble :
> >
> > If open properties of a table, to adding a column i.e., and that table
> > has some constraints, the SQL tab show code similar to :
> >
> > ALTER TABLE circulation.deliveries ADD CONSTRAINT
> > deliveries_delivery_type_id_fk FOREIGN KEY (delivery_type_id)
> > REFERENCES circulation.deliveries_types (delivery_type_id) MATCH
> > SIMPLE
> > ON UPDATE RESTRICT ON DELETE RESTRICT;
> >
> > ALTER TABLE circulation.deliveries DROP CONSTRAINT
> > deliveries_delivery_type_id_fk;
> >
> > (there are other constraints, deleted for easing the lecture)
> >
> > which cause an error because constraint already exist: DROP is after
> > ADD. And these code should not appears at all, because I did not any
> > change to these constraints. Usually says "--nothing to change" or
> > similar.
> >
> > It is a bug or I am doing anything wrong ?. I guess I am using revision
> > 4442.
> >
> > Regards,
> > Diego.
> >
> >
> >


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match