MES Core Dispatch - Revision history

Takacsjd: /* Summary */

2019-04-30T16:52:07Z

Summary

← Older revision		Revision as of 16:52, 30 April 2019
Line 4:		Line 4:

	Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS		Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS
			Planning Schema here: https://docs.google.com/spreadsheets/d/1JKVFx0xgw08Gk_61T2_X7q8RyJNv7TkhCJc2v7jy7yY/edit#gid=0

			NOTE: THIS IS IN PROGRESS - Documentation will float between here and google drive folders. final design will reside on wiki and will link to requisite other files.

	=Primer on SQL=		=Primer on SQL=

Takacsjd: /* Primer on SQL */

2019-04-30T16:07:12Z

Primer on SQL

← Older revision		Revision as of 16:07, 30 April 2019
Line 6:		Line 6:

	=Primer on SQL=		=Primer on SQL=
			SOURCE: https://stackoverflow.com/questions/6015175/difference-between-view-and-table-in-sql - Thank you everyone at Stack Overflow.

	SQL views - A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT FROM view		SQL views - A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT FROM view
	**So the view is actual a table that was made by a select statement. The view is stored and can be accessed so what would be the different between creating a new table with that information instead of a view.		**So the view is actual a table that was made by a select statement. The view is stored and can be accessed so what would be the different between creating a new table with that information instead of a view.
	***You can think of a view as a "saved select statement" that you can repeat. It's not really a table; even though some databases allow to create views that have a real table beneath, it's really just a SELECT statement which returns results.		***You can think of a view as a "saved select statement" that you can repeat. It's not really a table; even though some databases allow to create views that have a real table beneath, it's really just a SELECT statement which returns results.
	*Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.		*Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.

	=SQL architecture=		=SQL architecture=

Takacsjd: /* SQL architecture */

2019-04-30T16:06:27Z

SQL architecture

← Older revision		Revision as of 16:06, 30 April 2019
Line 4:		Line 4:

	Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS		Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS

			=Primer on SQL=
			SQL views - A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT FROM view
			**So the view is actual a table that was made by a select statement. The view is stored and can be accessed so what would be the different between creating a new table with that information instead of a view.
			***You can think of a view as a "saved select statement" that you can repeat. It's not really a table; even though some databases allow to create views that have a real table beneath, it's really just a SELECT statement which returns results.
			*Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.

	=SQL architecture=		=SQL architecture=
	*SQL Architecture:		==Summary==
	**Primer -		This is to cover the architecture of the SQL Schema that this module of the MES uses.
	**SQL views - A SQL view is ~~an aggregate~~ of ~~many~~ SQL ~~table columns~~ that ~~makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store~~ the ~~data in this usable joined together format. For instance, you will likely want a table that~~ uses ~~columns from products orders and traceability to show what product serial numbers are with what customer~~. A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT FROM view		==Tables==
	***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.
			==Views==
	**Orders Master Table View		**Orders Master Table View
	***Overview: This table shows the current placed orders and links to the customer that placed it. Also has keys to		***Overview: This table shows the current placed orders and links to the customer that placed it. Also has keys to

Takacsjd: explaining views

2019-04-30T16:03:08Z

explaining views

← Older revision		Revision as of 16:03, 30 April 2019
Line 8:		Line 8:
	*SQL Architecture:		*SQL Architecture:
	**Primer -		**Primer -
	***SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer.		**SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer. A table contains data, a view is just a SELECT statement which has been saved in the database (more or less, depending on your database).The advantage of a view is that it can join data from several tables thus creating a new view of it. Say you have a database with salaries and you need to do some complex statistical queries on it. Instead of sending the complex query to the database all the time, you can save the query as a view and then SELECT FROM view
	***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.		***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.
	**Orders Master Table View		**Orders Master Table View

Takacsjd: /* Summary */

2019-04-30T14:55:01Z

Summary

← Older revision		Revision as of 14:55, 30 April 2019
Line 2:		Line 2:
	This process kicks off other processes and decides what to do next.		This process kicks off other processes and decides what to do next.
	It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.		It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.

	Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS		Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS

Takacsjd: /* Summary */

2019-04-30T14:54:53Z

Summary

← Older revision		Revision as of 14:54, 30 April 2019
Line 2:		Line 2:
	This process kicks off other processes and decides what to do next.		This process kicks off other processes and decides what to do next.
	It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.		It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.
			Flow-charting here: https://drive.google.com/open?id=1nbcKawBKlytV8pOt1KDGsfpVsShDCZLS

	=SQL architecture=		=SQL architecture=

Takacsjd: Orgin

2019-04-30T14:54:15Z

Orgin

New page

=Summary=
This process kicks off other processes and decides what to do next.
It is the heart of the MES and directly interacts with customer orders, returns and other data to decide how to manage all other processes.

=SQL architecture=
*SQL Architecture:
**Primer -
***SQL views - A SQL view is an aggregate of many SQL table columns that makes the data more presentable and easy to use. It avoids forcing the user to Join many tables to get stuff done. Instead these views store the data in this usable joined together format. For instance, you will likely want a table that uses columns from products orders and traceability to show what product serial numbers are with what customer.
***Foreign keys - when the ID (one ID pre row is critical) of another table is used in this table.
**Orders Master Table View
***Overview: This table shows the current placed orders and links to the customer that placed it. Also has keys to
***Columns:
****PID - Foreign key to the Products table for what product is ordered
****Qty - how much was ordered
**Products Master Table View
***Columns:

**Traceability Master Table View
***Columns:
**Customer Data Table View