But this forces us to think about how primary keys are generated. We wouldn't want you to have to type in your own auto-incrementing ID.
Options:
Hide the primary key field (or at least make it not editable). The problem here is sometimes primary keys can be something other than the auto-incrementing ID.
Force dataface tables to use an auto-incrementing ID for the primary key, then make it not editable (and perhaps hide it).
The schema of the table should include the default attribute of each field. If it's set to "autoincrement" (or whatever it's called in postgres), prevent it being editable (at least on new records). I think this one's ideal.
But this forces us to think about how primary keys are generated. We wouldn't want you to have to type in your own auto-incrementing ID.
Options:
default
attribute of each field. If it's set to "autoincrement" (or whatever it's called in postgres), prevent it being editable (at least on new records). I think this one's ideal.