Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scripts _draft directory was skipped when db runs latest version #66

Closed
rdagumampan opened this issue Mar 6, 2020 · 1 comment
Closed
Assignees
Labels
bug Something isn't working

Comments

@rdagumampan
Copy link
Owner

rdagumampan commented Mar 6, 2020

Scripts _draft directory was skipped when db runs latest version

How to reproduce:

  1. yuniql init
  2. Add scripts to v0.00
  3. yuniql run
  4. Add scripts to v0.01
  5. yuniql run

Expected results:

  • Scripts in _pre, _draft and _post must be executed all the time

Actual results:

  • yuniql says the databases already runs the latest version, all directories were skipped
@rdagumampan rdagumampan added the bug Something isn't working label Mar 6, 2020
@rdagumampan rdagumampan self-assigned this Mar 6, 2020
@rdagumampan
Copy link
Owner Author

Fixed available in next release.
b353031

To support _draft, developer/data engineers need to handle repeated execution of scripts placed in _draft directory. For example, dropping the procedure before creating them.

DROP PROCEDURE IF EXISTS dbo.usp_get_employees;
GO

CREATE PROCEDURE dbo.usp_get_employees
AS
     SELECT * FROM dbo.employees;
GO

@rdagumampan rdagumampan added this to the v1.0 milestone May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant