Replies: 6 comments 2 replies
-
That's odd. Can you paste an example of the problematic line? The Plan parser defines the format of a plan, but a note is allowed to be any character at all aside from a newline, which can be stored as the literal strings |
Beta Was this translation helpful? Give feedback.
-
Sure, here's a sanitized version of the deploy script: -- Deploy misc script
-- Documentation link: https://jira_url.com/wiki/pages/viewpage.action?spaceKey=SPACE_NAME&title=PageTitle
USE WAREHOUSE &warehouse;
CREATE TABLE IF NOT EXISTS A.B (
C DATE,
D NUMBER(38,0)
); This was causing an error with the following message: |
Beta Was this translation helpful? Give feedback.
-
Oh, I thought you mean in the plan file. This syntax is defined by the SnowSQL client. Note the |
Beta Was this translation helpful? Give feedback.
-
Ok, thanks a lot then, you gave me all the info I needed! 👍 |
Beta Was this translation helpful? Give feedback.
-
You can also edit that line in the file directly, It's just informational, doesn't affect any business logic at all aside from the hash digest used to identify the file itself (so don't change it after you've tagged and released). Mind if I move this issue to discussions? Might help others in the future. |
Beta Was this translation helpful? Give feedback.
-
Yup, on our end it just means that having URLs in the scripts are a bad habit, and in the future it's better to put them in the plan for instance, where they would not be parsed in the comments. No problem to move it to Discussions! And again thanks a lot for your quick and efficient answers! 🙂 |
Beta Was this translation helpful? Give feedback.
-
Hi there, beginner users of sqitch here 👋
We had an issue, with a comment containing a URL to some wiki page, and the URL included the ampersand character.
This caused the execution of the
sqitch deploy
command to fail, and it was not immediately clear for us what caused the failure.My question is: is there someplace in the documentation indicating explicitly what is interpreted by sqitch at different stages, and what are the best practices when it comes to documenting the deploy scripts?
I found this section to be somewhat related, but I felt it was not really answering the question I had.
Beta Was this translation helpful? Give feedback.
All reactions