-
Notifications
You must be signed in to change notification settings - Fork 28
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
feat: add decimal/numeric support #620
Conversation
chore: add a Code of Conduct (googleapis#604)
fix: lint_setup_py was failing in Kokoro is now fixed (googleapis#607)
fix: Remove un necessary file from code base (googleapis#608)
feat: move migrations test modules to run against different emulator …
feat: update workflow files to uniformly distribute the test modules …
feat: update docs and nox file to compile it (googleapis#610)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM. My only concern is that the precision and scale of the Cloud Spanner NUMERIC
should be clearly documented as I believe other databases support arbitrary precision NUMERIC
.
38f030e
to
3d014ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we un-skip the django DecimalField
tests now?
python django_tests/django/tests/runtests.py 'model_fields.test_decimalfield.DecimalFieldTests'
I see failures in test_fetch_from_db_without_float_rounding
and test_fetch_from_db_without_float_rounding
, probably worth checking if these are real errors here and only skipping the tests we need to.
Looks like we can revert #400 now too.
LGTM after getting the django tests to pass (or skipping if impossible) and splitting out the system tests.
61e63f7
to
489f1c2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you need to update DatabaseValidation
for the tests to run?
removed validation for decimal field not supported by spanner. |
most of these tests are currently running. The 2 skipped ones we cant add back because Spanner doesn't support them. Checked. Reverted #400 . |
… thrown by python spanner decimal/numeric validation
…into decimal_numeric
…ation is not required
…jango into decimal_numeric
Workflows had issues yesterday Incident link so had to close and reopen the PR multiple times to retry all the actions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few non-blocking comments, feel free to merge it when you're ready.
…level in test_lookups
feat: added decimal/numeric support
Code changes involved:
fixes #617