Re: Foreign key constraint semantics?

[Ann Harrison]

The server group has designed an implementation of foreign
keys which is standard compliant (without MATCH PARTIAL, if
memory serves). The design goal is to support all engines
and cross engine constraints. That is the implementation
Falcon will use.

For the first version, it is likely that cascade / set null /
set default will be available only for transactional engines.
There are also open questions on the handling of foreign keys
in federated, blackhole, and archive.

Regards,


Ann