Acknowledged. I’m new around here and happily building away on top of several tables in a database now. It sounds like handling field uniqueness is the province of the application in Baserow world, so I’ll note that and handle as needed. I’m looking for any general advice on how to approach wanting to use fields other than the id for row lookups. A couple of reasons that first come to mind:
- It is common in publishing to use “slug” fields as a primary lookup key even if it isn’t the primary key on the table, with the assumption the field is constrained to be unique. You may be familiar that Django’s generic views can fetch objects by slug only. A corollary feature to this is allowing any unique field to be used in row lookups…
- Having the row ID in the URL may not be desirable for several reasons for some sites
Has anyone dealt with maintaining their own unique constraint for Baserow fields?