I. How to set the auto-increment of the INT-type primary key fields?
Now the answer is: set this field as the primary key and set only the get attribute.
However, my current requirements cannot be met, or my design is unreasonable. The following describes my design.
, Linkman is shared by apply and course, so I didn't set the contain relationship, but used reverse reference (fkreversequery ). However, it is meaningless for linkman to exist independently, so it does not have to design an independent service class, but is saved as attributes of apply and course when they are saved. Because it is a reverse reference, apply and course respectively store a linkmanid attribute. When applying or course is created, create and save linkman first, obtain the ID of linkman in the database and set its attributes, and then save apply or course itself. Therefore, according to this design, I have to let the primary key ID of linkman increase by itself, but also need it to be configurable. In the current nbear version, I don't know how to do it.
Ii. How to Use transactions?
This is also the demand derived from the above design. When saving, ensure that linkman and apply both succeed or fail at the same time. We can see that nbear has the transaction function, but we don't see any examples.CodeOr instructions, so I hope you can get some advice.
