GeoLocation网络应用程序的数据库建模 [英] Database Modeling For GeoLocation Networking App
问题描述
您好，
我正在尝试创建一个Geo-Location网络移动应用数据模型。我不确定我是否覆盖了所有人，因此希望得到数据建模专家的建议......
我正在努力识别实体和它的属性。我需要你们的帮助，如何在用户表中注入&bbsp
1）linkedIn帐户
2）如果用户使用电子邮件注册，
3）我们如何获得用户之间链接的消息。 （在这里混淆）
4）我认为我们需要将当前位置存储到Users表中的lat和long字段，以便立即检索和记录到Location_history表。
任何帮助都会很有用....
1.用户（主表）
2.连接
3.留言
4.技能（主表）
5.职业（参考用户）
6. UserSkill（参考技能和用户）
7.教育（参考用户）
用户可以登录使用LinkedIn帐户或使用电子邮件和密码注册。如果他们使用他们的电子邮件地址注册，那么他们需要激活已发送到他们的电子邮件地址的帐户，因此保持活动或不活动的属性需要
在用户实体中。
varchar需要什么密码字段，哈希值是多少......现在想的太多了多少b $ b用户
------ -------------------------------------------
user_account_ID AUTONUMBER
PK
Date_Joined 日期
DOB 日期
Email_Address Varchar
密码
LinkedInID Varchar
First_Name Varchar
Middle_Name Varchar
Last_Name Varchar
性别 Varchar（1）
Other_Details Varchar
ProfileImage
Geo-Lat Float
Geo-Long 浮动
isLive 位
Location_History
------------------------------------------------
user_account_ID 编号
复合PK Fk（用户）
start_date 日期时间
复合PK
end_date 日期时间
Geo-Lat Float
Geo-Lo ng Float
技能
------------------------------------- -----------
skill_ID 数字
PK
skillName Varchar
description Varchar
--isLive 位
UserSkill
----------------------------- -------------------------------------
$
user_account_ID 数字
复合PK，FK（用户）
skill_ID < span style ="white-space：pre"> 数字
复合PK，FK（技能）
职业/经验
------------------------------ --------------------------------------
us er_account_ID 数字
----复合PK FK（用户）
start_date 日期
----复合PK
end_date 日期
----复合PK
job_title Varchar
company_name Varchar
is_current_job 位
is_freelance_work 比特
job_location_city Varchar
job_location_state Varchar
job_location_country Varchar
description Varchar
教育
--------------- ----------- --------------------------------------------
user_account_ID 数字
----复合PK FK（用户）
degree_name Varchar
----复合PK FK
major Varchar
institute_university_name Varchar
from_date 日期
to_date date
问题
-------------------- ----------------------------
问：关于职业，我们是否需要城市，州或国家，我没看到原型中的城市，州或国家
答：没有¥b $ b
问：关于教育，我们是否需要城市，国家或国家，我不知道在原型中查看城市，州或国家
A：否
问：我们是否需要存储用户所在地的历史记录A：是的，位置的历史将由前端应用程序完成（Java微服务，用于跨平台应用程序开发的React本机）
问：我们是否需要滥用用户报告？
答：是
问：搜索
答：对于搜索功能，我们可能必须有一个非规范化表并将其映射到aws弹性搜索。但我们可以稍后讨论。我们希望搜索功能更快。
请注意这需要讨论更多
问：但是将技能存储到技能表中我们可以将它们像科学或数学或IT一样隔离，但只允许用户单独选择技能吗？是
A：是
所以需要FieldMaster和Skill Master表.....
Hello,
I am trying to create a Geo-Location networking mobile app DATA MODEL. I am not sure if i have covered all so wanted to get advice from experts who are data modelers......
I am evovling in identifying the entities and its attributes. I would need some help from you guys on how the
1) linkedIn account can be injected in Users table
2) what if User register using email,
3) how do we get the messages linked between users. (confused here)
4) I think the we need to store the current location to the Users table to lat and long fields so it is instant retrieval and history to Location_history table.
Any Help would be of great use....
1. User (Master table)
2. Connection
3. Message
4. Skill (Master table)
5. Occupation (Reference to User)
6. UserSkill (Reference Skill and User)
7. Education (Reference to User)
Users can either logon using LinkedIn account or register using email and password. If they Register using their email address then they would need to activate the account thats been sent to their email address, so an attribute to hold active or not needs to
be in the User Entity.
What would be the password field does it need to varchar and to have hash values... huh too many to think about now
Users
------------------------------------------------
user_account_ID AUTONUMBER
PK
Date_Joined Date
DOB Date
Email_Address Varchar
Password
LinkedInID Varchar
First_Name Varchar
Middle_Name Varchar
Last_Name Varchar
Gender Varchar(1)
Other_Details Varchar
ProfileImage
Geo-Lat Float
Geo-Long Float
isLive bit
Location_History
------------------------------------------------
user_account_ID Number
Composite PK Fk (Users)
start_date Datetime
Composite PK
end_date Datetime
Geo-Lat Float
Geo-Long Float
Skills
------------------------------------------------
skill_ID Numeric
PK
skillName Varchar
description Varchar
--isLive bit
UserSkill
------------------------------------------------------------------
user_account_ID Numeric
Composite PK, FK (Users)
skill_ID Numeric
Composite PK, FK (Skills)
Occupation/Experience
--------------------------------------------------------------------
user_account_ID Numeric
---- Composite PK FK (Users)
start_date date
---- Composite PK
end_date date
---- Composite PK
job_title Varchar
company_name Varchar
is_current_job Bit
is_freelance_work Bit
job_location_city Varchar
job_location_state Varchar
job_location_country Varchar
description Varchar
Education
----------------------------------------------------------------------
user_account_ID Numeric
---- Composite PK FK (Users)
degree_name Varchar
---- Composite PK FK
major Varchar
institute_university_name Varchar
from_date date
to_date date
Questions
------------------------------------------------
Q : Regarding occupation, do we need of city, state or country, i dont see city, state or country in the prototype
A : No
Q : Regarding Education, do we need of city, state or country, i dont see city, state or country in the prototype
A : No
Q : Do we need to store the histroy of location of users been too
A : Yes, and the history of location will be done by the front end app (Java micro services, React native for cross platform app development)
Q : do we need to have report abuse about user?
A : Yes
Q : Searching
A : For searching capability we might have to have a de-normalized table and map it to aws elastic search. But we can discuss that later. We want the search functionality to be fast.
PLEASE NOTE THIS NEEDS TO DISCUSSED MORE
Q : but while storing the skills to skills table can we segregate them like science or maths or IT but just allow users to select the skills alone?
A : Yes
So FieldMaster and Skill Master tables required.....
谢谢
Senthil
推荐答案
非常感谢任何帮助......
Any Help is much appreciated....
这篇关于GeoLocation网络应用程序的数据库建模的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
