#1 Changing a value in primary key

[Anonymous]

In 0.5.1: Changing a value that is part of a
primary key does not work - both for
single-value primary keys and multi-value keys.

The problem is that the "old" value is needed in
the WHERE-statement to be able to run a proper
UPDATE to the new values.

An early attempt to patch this problem revealed
that although it is easy to include such value
changes in the "SET"-part of the SQL, it doesn't
make much sence as the WHERE-part will
reference NEW values - updating 0 rows. (or
possible OTHER rows).

Now - at least this is detected in CVS version, but
it should really be possible to change such value.
This is rather important for glue tables where all
columns are part of the "primary key".

(what needs to be done is some way of storing
the old value. This could possibly be part of a
larger rewrite to only update those columns that
have been changed in the object attributes,
instead of overwriting whole row.)

[Stian Soiland-Reyes]

Issue moved to https://github.com/stain/forgetSQL/issues/1