Does OpenAccess ORM support ID fields that are not integer types (i.e. not short, int, long)?
The reason I ask is that there are some tables with a LOT of additions and deletions over time, so you eventually hit the int.maxValue limit and need to reset the seed through database administration. There are some tables where we have a natural key that is a nvarchar string, for example. Suppose the table stores website URL links and the associated IP address of the host. Ideally, in that case, I would want:
- An entity model with a URL:String & IP:String field that map to nvarchar and varchar repsectively in the database.
- URL is set as the primary key, and OpenAcess does not try to go ahead and create its own integer based ID field as it does today (which results in the same problem)
This not only saves database space for a very large table, but also makes management easier. I agree that for moderately sized tables, an integer based ID is the best way to go, and it is what I do.