Closed ishepherd closed 1 year ago
OK I get it - Seems that the checksum isn't part of change detection? This tool runs a certain script filename once and never again, by design.
This seems bad for stateless objects (Stored Procs, Views, etc), you have to rename the file every time you want to edit the object? Surely this will break git blame
and things like that?
Am I missing something?
There is a way to detect changes, but currently the only way to do so is to use the incremental builds in Packages, which would track the file changes on the client side. You would do something like
# Create a package first
New-DBOPackage -Path package.zip -ScriptPath .\myfunctions -Build 1.0.0
# add files, as they get created or modified
Add-DBOBuild -Path package.zip -ScriptPath .\myfunctions -Type New, Modified
# install the package
Install-DBOPackage -Path package.zip ...
OK, thanks!
Hi 👋 thankyou for this project.
I'm finding that this cmdlet, though it finds the file, never runs it? It seems to run it once and never again, even if it changed. I assumed it tracks the checksum in
SchemaVersions
for the purpose of detecting a change?Expected behaviour: Content has changed => script is run again.