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

Using the max_existing_timestamp macros on a new table throws an error #87

Closed
njuguna-n opened this issue May 23, 2024 · 3 comments
Closed
Assignees
Labels
Type: Bug Fix something that isn't working as intended

Comments

@njuguna-n
Copy link

When starting a new sync process all models using the max_existing_timestamp throw the error below. The error is not thrown if the tables have already been created and have some data.

invalid input syntax for type timestamp: "None"
  LINE 38:   AND "@timestamp" >= CAST('None' AS TIMESTAMP)
@lorerod
Copy link
Contributor

lorerod commented May 23, 2024

@njuguna-n did you tried with the changes made in max_existing_multiro_macros.sql in this commit?

@njuguna-n
Copy link
Author

@lorerod yes. I have also tried usingNull instead of None

@andrablaj
Copy link
Member

Closing this issue as it was marked as Done and the related PR was merged.

@andrablaj andrablaj added this to the CHT Sync Production milestone Jun 6, 2024
@andrablaj andrablaj added the Type: Bug Fix something that isn't working as intended label Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Fix something that isn't working as intended
Projects
Status: Done
Development

No branches or pull requests

3 participants