This repository has been archived by the owner on Dec 21, 2022. It is now read-only.
Skipping sync of users that are already up to date from last known date #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * @return string | ||
| */ | ||
| public static function convert_date_to_ymd($value) { | ||
| $date = DateTime::createFromFormat('YmdHis.0Z', $value); |
There was a problem hiding this comment.
I'd add a note here that LDAP uses GeneralizedTime format, and that we assume it will never supply tenths-of-a-second (i.e. this is always zero) and that it will always supply it as UTC (i.e. Z at the end). At least I hope these assertions hold...
mateusz
added a commit
that referenced
this pull request
Mar 24, 2015
Skipping sync of users that are already up to date from last known date
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.