Guest User

Untitled

a guest
Nov 16th, 2018
94
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.55 KB | None | 0 0
  1. ## Preparations:
  2. Generate password to be used
  3.  
  4. ## Process
  5.  
  6. 1. Update puppet script in e.g database_qa.pp, database_test.pp etc
  7. --> Ensure -> "absent" / "purged"
  8. --> Create a new database, postgres
  9. --> Use A or B of the postgres database servers? A?
  10. 2. Change the configuration files (Must be done in steps). No changes for the production configuration!!
  11. 2a. DO NOT DEPLOY BEFORE READY!
  12. 3. Change the datatypes in the "changelog files" - liquibase
  13.  
  14. ## Moving the data, yo:
  15. 1. Delete tables in posgres?
  16. 2. Shut down service
  17. 3. run pgloader?
  18. -- Connecting to one database and copy the data from one to another (between types as well - e.g mysql => postgres)
  19. 4. Have to alter the tables to be schema public, not the actual database schematics
  20. 5. delete some triggers? wth
  21. 6. Add the two-hours difference for any datetime stuff
  22. 7. Add some triggers? wth
  23. 8. Deploy to prod
  24. 9. Check πŸ™ˆ
  25. 10. next build: `ALTER TABLE databasechangelog RENAME COLUMN comments TO "COMMENTS"`
  26.  
  27. ## Problems/Gotchas:
  28. - Uppercase / Lowercase problems in Postgres
  29. - Be aware of the timezone of the posgres database compared to the MySql database
  30. - Can be detected by checking the created timestamps
  31. - Can be fixed by changing from new Date() => ZoneDateTime
  32. - AUTO_INCREMENT => CREATE SEQUENCE (or equialent of the auto_increment option)
  33. - "now" value => mysql :: postgres
  34. - Dateformats requires extra treating. date_format() => to_char('', '<dateformat>')
  35. - Add a flag for the dataSource communitions?
  36. - Stuck on darn changelog syncronizations in regards to Liquibase?
  37. - `b liquibase-migrate -p changelogSync `
Add Comment
Please, Sign In to add comment