Timeline for Is there a best practice for resolving dependencies of SQL objects for build during development?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2023 at 16:03 | comment | added | J.D. | @alx9r The term migrations in this context means schema migrations. It doesn't literally mean to migrate from one database system to another, or even one database to another (necessarily), but rather to migrate one implementation / version of your schema to the next version as you make changes to your design. "I have to manually re-resolve the order of the files defining the objects are executed" - That's you manually migrating your schema to a new version. I'll admit, the first time I heard the term, it confused me for a few minutes too, but it's just a synonym for revision control. | |
| Feb 26, 2023 at 14:53 | comment | added | alx9r | I'm puzzled by this answer as my question isn't about migrating a database. Rather, my question is about creating a new database from source code. There's no production data yet, so no data to migrate. So I'm not sure how to interpret this answer. Do you mean that a database migration tool would resolve dependencies of SQL objects defined in source code? Do you mean that instead of source code being the authoritative definition during development, an output from a migration tool should be the authoritative artifact instead? Or do you mean something else? | |
| Feb 26, 2023 at 4:05 | history | answered | J.D. | CC BY-SA 4.0 |