这在SQL中是什么样的方法，它确实存在？(What kind of approach is this in SQL, it actually exists? Is it viable/good pratice?)

 我们的一位老师给了我们以下挑战： 
 
 
 
 “使用以下原则创建数据库模式：您不能更改任何表上的任何值，只能添加新值。” 
 
 
 我带来了以下架构： 
 
    CREATE TABLE TRANSACTIONS(ID PRIMARY KEY, TRANSACTION_TYPE_FK, DATE);

    CREATE TABLE TRANSACTION_TYPE(ID PRIMARY KEY, NAME);

    CREATE TABLE PRODUCTS_TRANSACTIONS(ID_PROD_FK, ID_TRANS_FK, MONEY,  QTY);

    CREATE TABLE PRODUCTS(ID PRIMARY KEY, NAME, PRICE_FK );

    CREATE TABLE PRICES(ID PRIMARY KEY, DATE, DETAILS);
 
 这只是一个概念证明。 基本上一切都基于交易。 
 
 交易可以是进入，退出和移动产品以及进出货币。 
 
 我可以根据交易控制我的数量和现金。 
 
 如果交易仅涉及金钱或交易中存在“折扣”或“税”，则使用PRODUCTS_TRANSACTIONS“MONEY”字段。 
 
 产品表有一个名为“价格”的“子”表，它存储所有价格变化，“详细信息”字段用于“成本价”等注释。 
 
 我做得很快，对于任何不一致我很抱歉。 
 
 我喜欢这种方法，我有点像SQL的新手所以我真的想知道这种方法是否有名称，如果它是可行的性能或良好的实践。 
 
 我的想法是在制作新事务时创建一个View并“更新”它，因为没有什么需要“更新”我只需要向View添加新行。 
 
 我目前病得很重，所以我不能上大学来解决我的疑虑。 
 
 在此先感谢您的帮助 

One of our teachers gave us the following challenge:
 
 
 
"Make a Database schema with the following principle: you can't change any values on any table, only add new ones."
 
 
I came with the following schema:
 
    CREATE TABLE TRANSACTIONS(ID PRIMARY KEY, TRANSACTION_TYPE_FK, DATE);

    CREATE TABLE TRANSACTION_TYPE(ID PRIMARY KEY, NAME);

    CREATE TABLE PRODUCTS_TRANSACTIONS(ID_PROD_FK, ID_TRANS_FK, MONEY,  QTY);

    CREATE TABLE PRODUCTS(ID PRIMARY KEY, NAME, PRICE_FK );

    CREATE TABLE PRICES(ID PRIMARY KEY, DATE, DETAILS);
 
It's just a proof of concept. Basically everything is based on transactions.
 
Transactions can be Entry, Exit and Move Products and In & Out Money.
 
I can control my quantities and cash based on transactions.
 
The PRODUCTS_TRANSACTIONS "MONEY" field is used if a transaction involves money only or there are "discounts" or "taxes" on the transaction.
 
The Products Table has a "child" table called "prices", it storages all the price changes , the "details" field is for annotations like "Cost Price" etc.
 
I made it very quick, I am sorry for any inconsistency.
 
I liked this kind of approach, I am kinda of a newbie with SQL so I really wanted to know if this approach has a name and if it is viable perfomance-wise or a good pratice.
 
My idea is making a View and "update" it whenever a new transaction is made, since nothing needs to be "updated" I only need to add new rows to the View.
 
I am currently very sick, so I can't go to college to remedy my doubts.
 
Thanks in advance for any help

原文：https://stackoverflow.com/questions/39364311