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

Add milliseconds to SQLite datetimes #12

Merged
merged 5 commits into from
Sep 24, 2021
Merged

Conversation

ItachiSan
Copy link
Contributor

The SQLite DATETIME() method does not provide milliseconds nor has a switch for toggling them.
This is overall inconvenient.
By calling correctly STRFTIME(), we can have the milliseconds information appropriately added.

In addition, the CI configuration file was updated to support newer Python and SQLAlchemy versions.

The SQLite DATETIME() method does not provide milliseconds nor has a
switch for toggling them.
This is overall inconvenient.
By calling correctly STRFTIME(), we can have the milliseconds
information appropriately added.

In addition, the CI configuration file was updated to support newer
Python and SQLAlchemy versions.
Copy link
Contributor

@dahlia dahlia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you write a test case to ensure if the utcnow() expression within SQLite dialect emits the precise datetime.datetime value?

@ItachiSan
Copy link
Contributor Author

I can definitely do that! How much of an overhead should I have? 0.5 seconds?

- Tox environments for newer Python versions have been added
- Big improvements in Travis CI
  - Not testing agains EOL SQLAlchemy 0.9
  - Fetch correct dependencies versions for older Python envs
- Temporarily adjust the README for my personal branch, plus point to
  newer Travis CI (from .org it has unified in .com)
- Avoid testing older Python versions with SQLAlchemy v1.4 as no package
  is available for them
- Resolve the issue with the newer `pytest-cov` not working with older
  `pytest` by installing an older version where necessary
The double square brackets in Bash uses '&&' while the single square
brackets uses '-a'.
I essentially used the wrong convention here :P
Travis-CI can still keep up even on unsupported Python versions.
Just mention that those are unsupported and add references so that
in the future the deprecated versions can be removed easily.

Also, restore CI links to the official project.
@ItachiSan
Copy link
Contributor Author

Hi, is there any issue with the current pull request?
I was expecting this to be merged sooner or later.

Copy link
Contributor

@dahlia dahlia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good to me. @pbzweihander could you please take a look?

Copy link
Contributor

@pbzweihander pbzweihander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, too!

@pbzweihander
Copy link
Contributor

@Jhuni0123 Could you review and merge this PR?

Copy link
Contributor

@Jhuni0123 Jhuni0123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Good. Thanks for your contribution!

@Jhuni0123 Jhuni0123 merged commit 14482ea into spoqa:master Sep 24, 2021
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

Successfully merging this pull request may close these issues.

4 participants