Add support for custom PK names, hidden attributes, and different DB connections #10
Conversation
This file contains hidden or 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
…efer to insertId with the getKey() function to allow for use on models where the PK is not 'id'. Put in a check for the DB::connection to allow for use on multiple DBs. Check against the fields on the model (which toArray() will check against)
Contributor
|
Hey @chalcedonyt would you be able to add your changes to the changelog as well? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
incrementingmodel property to determine whether it is a uniqueIdgetKeymethod instead of assuming it's calledidhiddenattributes on the model when creating the bigq table - this is becausetoArrayignores them too.DB::connection