-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Configurable user model & new aggregate value #34
Conversation
Adding SECOND as aggregate option, and adding User Model configuration variable.
1. Making user relation configurable. 2. Adding SECOND aggregate to set microsecond to 0 MSSQL isn't getting microseconds as 0. - Value before changes: 2024-04-29 00:00:00.950 New code now set microsecond to 0. - Value after changes: 2024-04-30 00:00:00.000 Note: Migrate haven't been modified. Date column type is datetime.
In our side, now the counter updates as expected. |
Remove part from separate PR
Revert relationship changes
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.
Thanks @CyberEkklesiaOwner 👍
Hello @bilfeldt Thank you for accepting some changes. Is there anything wrong with the relationship changes? route-statistics.php & RouteStatistic.php updates were removed. Could those changes be added to make user model configurable? At least similar to logger... |
@CyberEkklesiaOwner sorry about the confusion. Can you please make a separate PR for the user model config, then I will happily merge that. |
Description
Making user model configurable and add SECOND aggregate to set microsecond to 0.
Does this close any currently open issues?
No. But the configurable model is needed to make code compatible with LdapRecord. LdapRecord, when using database configuration, the user relation is from auth.providers.users.database.model and not from auth.providers.users.model. Therefore, both packages won't work together. As of now, a custom model is required.
The aggregate is needed for MSSQL. Currently, once date is inserted, the datetime value still accepting time other than 0.
Before aggregate: 2024-04-29 00:00:00.950
After aggregate: 2024-04-30 00:00:00.000