Hello, I’m curious about the reasoning behind prefixing the table names when creating a new resource via context generator. What would be the recommendation in the case that someone does what the docs refer to when mentioning that a resource may be a part of different contexts:
Note a resource may also be split over distinct contexts (such as Accounts.User and Payments.User).
What would be the recommended table name here?
payments_users or something else?
I understand that you can change it, but being part of a generator somewhat implies that they want to drive the point that we should be thinking about things in terms of contexts and I’m curious what folks have to say about this.
Personally, I would just name my table
users, but I’d like to hear from others and get a sense of the conversion.