您将美国表称为什么？
对于大众来说是一个愚蠢的问题：假设您有一个表来处理对象通过工作流程时的状态。
现在假设您有一个标准的美国州表...
您如何称呼您的美国州表，而不是多余的？
附加约束 - 您不能使表复数。
一些想法：
UnitedState
StateOfUnion
UnionizedState
AmericanState
很好奇看看其他人想出了什么......
Silly question for the masses: Assume you have a table that handles the state of your object as it passes through your workflow.
Now assume you have a standard United States State table...
What do you call your US State table, without being redundant?
Additional Constraint - You can't pluralize your tables.
Some thoughts:
UnitedState
StateOfUnion
UnionizedState
AmericanState
Curious to see what other people come up with...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（11）
CountryDivision将非常全球化，并且有一个
Country表CountryDivisionwould be pretty globaland a
CountrytableUSAState
或者，如果您想在每条记录中包含国家/地区，请将其称为 GeographicState
USAState
Or if you want to include the country in each record call it GeographicState
StateProvince 存储州和省多个国家的省份
StateProvince that stores states & provinces in multiple countries
为什么必须更改地理状态表。为什么不将工作流状态表命名为 WorkflowState、WorkflowObjectState、ObjectState 等。
此外，我倾向于将地理状态放入内存集合而不是数据库中。
Why do you have to change the geographic states table. Why not name the Workflow States table WorkflowState, WorkflowObjectState, ObjectState, etc.
Also, I tend to put geographic states into in memory collections instead of the database.
地址状态怎么样？让它更加全球化......
What about AddressState? Keeps it a little more globalised...
省- 这涉及州和省（如某些国家/地区）。Provinces- This addresses both states and provinces as in some countries.我传统上使用
USStates来实现此目的，它是“United State's States”的缩写，完整版本比短版稍微不太直观……但短版就是您一直在查看的内容。其他一些示例：
AUStates- 澳大利亚MXStates- 墨西哥INStates- 印度只要使用国家/地区前缀即可，如果为每个国家/地区存储一组不同的数据，如果您不这样做，则首先不需要多个表。
I've traditionally used
USStatesfor this, short for "United State's States", the full version's a bit less intuitive than the short...but the short's what you're looking at all the time.Some other examples:
AUStates- AustraliaMXStates- MexicoINStates- IndiaJust using the country prefix works, if you're storing a different set of data for each country, if you're not doing that, there's no need for multiple tables in the first place.
我称之为“状态”
和另一个国家
i call one STATUS
and the other STATE
我使用过区域，但我们跟踪的不仅仅是州名称。我们希望能够通过地理定位来分解或构建其他区域，例如城市、社区、企业等
I've used Regions but we were tracking more than just the names of states. We wanted the ability to breakdown or buildup other areas by geoloc such as cities, neighborhoods, businesses, etc
USGeoState怎么样？How about
USGeoState?State_Squared 怎么样？
:^)
How about State_Squared ?
:^)