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

CURRENT_TIMESTAMP && CURRENT_DATE not support by auto migrations #163

Open
diyor28 opened this issue Feb 28, 2025 · 2 comments
Open

CURRENT_TIMESTAMP && CURRENT_DATE not support by auto migrations #163

diyor28 opened this issue Feb 28, 2025 · 2 comments
Labels
draft Work in progress

Comments

@diyor28
Copy link
Contributor

diyor28 commented Feb 28, 2025

No description provided.

@diyor28 diyor28 added the draft Work in progress label Feb 28, 2025
@twinguy
Copy link
Contributor

twinguy commented Mar 2, 2025

@diyor28 Can you provide a little more detail on what "auto" migrations are? Trying to reproduce what the exact steps are and specifically if this is in the "staging" branch or if this is in main.

Thanks very much.

@diyor28
Copy link
Contributor Author

diyor28 commented Mar 4, 2025

@diyor28 Can you provide a little more detail on what "auto" migrations are? Trying to reproduce what the exact steps are and specifically if this is in the "staging" branch or if this is in main.

Thanks very much.

I'm still working on the issue, I'll let u know once I remove the draft label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft Work in progress
Projects
None yet
Development

No branches or pull requests

2 participants