each table has only one Primary Key about sorm HOT 2 CLOSED

Solution 1

firstly,we should controll the user action:
If the @PrimaryKey keeps opening,it may cause some confuse to some users who not very fimiliar to database :we can define one more Primary Key in one table.

so,I will remove it.

1.default @table(name="tablename",id="__id")

• id means the PRIMARY KEY AUTOINCREMENT
• motify the id to custom you primar key

2.When saving and delete the model,take care of the id

Solution 2

Solution 1 looks nice,but it's hard to code.Every time you save or delete,you have to figure out the where the id is.

to be lazy is:
Not able to give a right to user to motify the id

from sorm.

use @unique instead of @PrimaryKey

from sorm.