汽车零部件数据库设计 [英] Database design for automobile parts

查看:105
本文介绍了汽车零部件数据库设计的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在开发数据库模型,然后开发汽车零件进口商的数据库。该公司从不同供应商进口不同的汽车产品。每个供应商可能拥有自己的同一物品的识别号码。客户在跟踪同一项目的订单时遇到问题,并且还需要比较提供相同的项目,即使它在不同的文档中被不同地引用。在采购订单之后,它需要跟踪来自不同供应商的订单的成功/失败。为了解决这个问题,我在数据库表中做了以下几点。

I am working to develop database model then the database for automobile parts importer. the company imports different car items from different suppliers. Each supplier is likely to have it own identification number for the same item. the problem the client faces issues in tracking orders of the same item and also needs compare offers the same items even though it is referred differently across different documents. after the purchase order, it needs to track the success /failure of orders from different suppliers. in order to approach the problem, I have made the following the database table.

<pre lang="SQL">

Suplier(身份证,姓名,联系方式)

项目(ID ,项目,数量)

ItemSuplier(ID,Item_ID(FK),Suplier ID,识别码,OE_Code,描述)



//识别码表示供应商用于物品的代码识别,根据供应商的不同而不同。 OE表示原始汽车制造商用于区分物品。

订单(ID,物料ID,数量)

子订单(ID,order_ID,供应商_ID ,数量,价格)

//子订单指示进口商何时发送订单不同的供应商发回物品的价格以及它们将提供多少。子订单是,进口商在比较不同的价格后会发送确认订单与他们选择发送的供应商。

所以我的问题是,这个数据库表足以解决问题了吗?还是需要一些改变?第二,如何在NeDB中实现?如果你给我你的建议,我将不胜感激。



我的尝试:



我一直在尝试为NeDb数据库中的系统构建数据库

Suplier(ID, Name, Contact)
Item(ID,Item, Quantity)
ItemSuplier (ID, Item_ID(FK), Suplier ID, Identification Code, OE_Code, Description)

// Identification code indicates, the code identification used for items by suppliers which is different according to the supplier. The OE indicate the original automobile manufacturer used to differentiate the items.
Order (ID, Item ID, Qty)
Suborder(ID, order_ID, Supplier _ID, Qty, Price)
// the suborder indicate when the importer sends the order different suppliers send back the price of the item and how many they are going to provide. the suborder is, importer after comparing different price will send the confirmation order with the supplier they chose to send.
so my question is, this database table enough to address the problem? or need some change? second, how can make it in NeDB? I would appreciate if you give me your suggestions.

What I have tried:

I have been trying to build the database for a system in NeDb database

推荐答案

引用:

这个数据库表足以解决问题?还是需要一些改变?

this database table enough to adress the problem? or need some change?

这种设计不太可能,你只有一个表可能是一个糟糕的设计。不幸的是,您的问题很难阅读。



以下是一些汽车行业数据库设计示例的链接

数据模型 - 汽车行业 [ ^ ]向您展示其他人如何做到这一点,但要注意,您的导师将非常熟悉该链接上的模型。



告诉如何在任何环境中创建数据库都是Quick Answers论坛的主题。我建议你参考作者的文档 GitHub - louischatriot / nedb:JavaScript数据库,用于Node.js,nw.js,电子和浏览器 [ ^ ]

It's highly unlikely that this design will be sufficient and it you only have one table it is likely to be a bad design. Unfortunately your question is very difficult to read.

Here is a link to some example Automotive Industry database designs
Data Models - Automotive Industry[^] to show you how other people have gone about this, but beware, your tutor will be very familiar with the models on that link.

Telling how to make your database in any environment is off-topic for a Quick Answers forum. I suggest you refer to the author's documentation GitHub - louischatriot/nedb: The JavaScript Database, for Node.js, nw.js, electron and the browser[^]


这篇关于汽车零部件数据库设计的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆