能够处理多个客户（客户） [英] Ability to handle multiple clients (customers)

问题描述

我已经创建了一个获取输入的工具，并且在验证后给出了O / p，我已经完成了PHP和Python的编程，并且我已经将工具与SQL服务器连接.....当用户给出了ai / p它转到SQL Server中的table_nameInput_Value然后我的工具获取数据并验证它，在验证结果后转到Table_nameOutput_Value。当另一个用户给I / p表值删除以前的用户时... .....如果两个用户同时尝试验证它们的值，那么结果会相互混合。

所以我可以使用什么逻辑，这样多个用户可以同时使用我的工具，他们会分别得到他们的结果。



我尝试了什么：



现在我只为一个用户使用逻辑。我有一个input_table和output_value表。当另一个用户尝试或相同的用户再次尝试以前的值被删除和新的值发生....如果多个用户同时尝试。

解决方案

基于您的设计，在多用户环境中，第一个进入的i / p可能会被下一个紧接的后续i / p删除，然后才能进行验证。并且无法确定验证的输出是否源自特定输入。此外，如果您不想保留输入的轨迹和相应的输出，为什么要使用数据库？

无论如何，如果你坚持要想想这个设计：

 输入表 输出表 
 input_id（主键）--- | output_id（主键）
 input_data | output_data 
 datatime | ---- input_id 
 datetime 

数据库设计简介 [ ^ ]

数据库规范化中的1NF，2NF，3NF和BCNF | DBMS教程| Studytonight [ ^ ]

i have created a tool that that takes the input and after validating gives the O/p, i have done the programming in PHP and Python and i have connected the tool with SQL server.....when a user gives a i/p it goes to a table_name "Input_Value" in SQL Server then my tool fetches the data and validate it, after validating result goes to Table_name "Output_Value".when another user gives I/p table values get deleted of previous user........if two user tries to validate their value at same time then result mix with each other.
so what logic can i use so multiple user can work on my tool same time and they will get their result separately.

What I have tried:

now i am using logic for one user only. i have one "input_table" and "output_value" table. when another user tries or same users tries again previous values get deleted and new values take places....what if multiple users tries at same time.

解决方案

Based on your design, in a multi-user environment, the first i/p that comes in may get deleted by next immediate subsequent i/p before it can be picked up for validation. and there is no way to be certain that an output from a validation originated from a particular input. Furthermore, if you do not want to keep the trails of the inputs and the corresponding outputs, why use a database?
Anyway, think of this design if you insist:

input table              output table
input_id (primary key) ---|     output_id (primary key)
input_data                |     output_data
datatime                  |---- input_id
                                datetime

Introduction to database design[^]
1NF, 2NF, 3NF and BCNF in Database Normalization | DBMS Tutorial | Studytonight[^]

这篇关于能够处理多个客户（客户）的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！