You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding of the purpose of Tutorial Parts 1-3 is to demo successively more complex mappings between the DB and Beam.
Can Part 3 rephrase "creating tables" to "creating new table mappings" or something similar to this? https://haskell-beam.github.io/beam/tutorials/tutorial3/
i.m.o. "creating tables" should be held back to describe the Migrations Framework.
The description in the Migrations Framework section helps me to clearly understand that Parts 1-3 do not actually create any tables in the database:
In the User Guide we saw how to declare a schema for an already created database and use it to perform queries. Beam can also manage a database schema based on Haskell datatypes you feed it.
The migrations framework is meant to be a robust and modular way of managing schema changes.
As I understand it:
Tutorial Parts 1-3 are concerned with Data Query Language and Data Manipulation Language.
Migrations Framework is concerned with Data Definition Language.
Can we add these phrases?
Thanks
The text was updated successfully, but these errors were encountered:
My understanding of the purpose of Tutorial Parts 1-3 is to demo successively more complex mappings between the DB and Beam.
Can Part 3 rephrase "creating tables" to "creating new table mappings" or something similar to this?
https://haskell-beam.github.io/beam/tutorials/tutorial3/
i.m.o. "creating tables" should be held back to describe the Migrations Framework.
The description in the Migrations Framework section helps me to clearly understand that Parts 1-3 do not actually create any tables in the database:
As I understand it:
Tutorial Parts 1-3 are concerned with Data Query Language and Data Manipulation Language.
Migrations Framework is concerned with Data Definition Language.
Can we add these phrases?
Thanks
The text was updated successfully, but these errors were encountered: