This repository has been archived by the owner on Dec 11, 2020. It is now read-only.
Improve name guesser logic using field length when available #606
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
…ctrine, Propel) and adds a few more field types.
| public function guessFormat($name) | ||
| /** | ||
| * @param string $name | ||
| * @param int $size |
fzaninotto
added a commit
that referenced
this pull request
Aug 24, 2015
Improve name guesser logic using field length when available
|
Great patch, thanks! |
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.
I kept finding dummy users with Lorem Ipsum as their salutation. This change uses the field length to be a bit more intelligent when that data is known. I've also tried to guess a few more column name and types.