Antoine, > the *users* table defines a foreign key to the *policy* one and the > default policy_id is 1. > > The problem(?) is I can't see any default policy provided with the SQL > schema, so the the first one created will become the default policy for > existing *users* records (with a policy_id == 1).
Well, yes. You are free to drop a DEFAULT attribute, or to provide some neutral policy record with id==1 during installation. > Is it an intended behaviour? Is '1' a reserved value? Not really intentional. A '1' is not special or reserved. The DEFAULT is there for the sole purpose of making it easier to add new user records, without having to specify a policy_id with each insert for a common case. Mark
