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

Review RDBMS data types e.g. should we add date/time types #2870

Open
michelleN opened this issue Sep 30, 2024 · 4 comments
Open

Review RDBMS data types e.g. should we add date/time types #2870

michelleN opened this issue Sep 30, 2024 · 4 comments

Comments

@michelleN
Copy link
Member

No description provided.

@michelleN michelleN converted this from a draft issue Sep 30, 2024
@michelleN
Copy link
Member Author

Adding more detail: This would require updating the WIT, the related factor(s), the sdks and cloud support.
Anything else required?

@vdice
Copy link
Member

vdice commented Nov 4, 2024

@michelleN @itowlson is this considered closed per #2895?

@itowlson
Copy link
Contributor

itowlson commented Nov 4, 2024

@vdice We've not done MySQL yet but we can close this in favour of a more specific issue if that would be preferable?

@vdice
Copy link
Member

vdice commented Nov 4, 2024

@itowlson no preference; my motivation is to clean up the 3.0 project/milestone. If we'd like to keep this open to track MySQL, let's just untether from 3.0 and move to 'Post-Release', even though one half (Postgres) is in.

@itowlson itowlson removed this from Spin 3.0 Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants