Populate DB with sensible data

[Dr-Crow]

Add all the classes, curricula, languages, employees, sites, etc. This makes it easier to test and just a nice experience when sourcing the DB.

[algozine]

The original requirement for this is coming from a discussion I had with Jimmy .. or rather an email first asking how it could be done, then a discussion. I want the names of the 28 classes from the full curriculum, and the 4 from the cornerstone class, and some of the other modified classes from the rehab location curricula that are NOW in the database running on .34 to be preserved so that we don't have to type them all in again. The Curricula would also be nice, but not needed, as we are changing some thing in that part of the DB (as I understand it). So... classes for sure.. maybe locations and curricula, employees for sure ... that would be great. Thanks

[jrands]

Marcos and I were discussing this as well, trigger functions would probably be the best way to populate the DB with some default values every time it is sourced. I'll begin working on this.

[Dr-Crow]

@jrands Hey john, no triggers needed. Lets use the /Test/ folder and populate some of this data using inserts. I will do a dump of the DB tonight or tomorrow to get all the classes that have been entered already.

[marcosb1]

https://stackoverflow.com/questions/12815496/export-specific-rows-from-a-postgresql-table-as-insert-sql-script

[marcosb1]

That should solve whatever issues you were having @Dr-Crow

[Dr-Crow]

Added data, waiting on employee info from new deploy or if the web team could get me that info. @michellecrawley ?

[michelleburd]

What kind of employee information do you need? Name, phone number, languages, classes taught, etc.? @Dr-Crow