On 10/25/2017 11:30 PM, Prasheel Soni wrote: > I have set the primary key(id) of authorization and challenges to > autoIncrement. > > I am facing the issue that for creating an order I need to first > insert a record in order entity leaving the authorizations field data > empty. Then further I need to create a record in authorization entity > which will provide me with the id (primary key) and this id is > required to create authorization's URL. > > so should I remove authorization id (PK) from autoincrement and > generate it randomly? The approach we are taking in Boulder is to treat the relationship between orders and authorizations as a many-to-many relationship. Each order can contain many authorizations, and each authorization can be contained in many orders. We represent this as a relationship table that has one column for order id, and one column for authorization id, created after both the order and the authorizations.
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
