-
Notifications
You must be signed in to change notification settings - Fork 562
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: aarondl/sqlboiler
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.10.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: aarondl/sqlboiler
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.11.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 9 files changed
- 4 contributors
Commits on Apr 20, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 445f482 - Browse repository at this point
Copy the full SHA 445f482View commit details -
Configuration menu - View commit details
-
Copy full SHA for d6eae87 - Browse repository at this point
Copy the full SHA d6eae87View commit details
Commits on Apr 25, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 3f46025 - Browse repository at this point
Copy the full SHA 3f46025View commit details -
Add getter methods to relationship structs
The goal of this change is to alleviate the need for the caller to check if the models' relationship struct is nil before accessing a field. Indeed, we've seen a proliferation in our codebase of the following pattern: ``` if record.R != nil && record.R.SomeField != nil { ... } ``` This is especially required in utilities functions which are not responsible for loading the model and can't know if the record has eagerly loaded the relationships and thus can't know if the relationship struct is nil. With this change, the previous code idiom can be replaced with: ``` if field := record.R.GetSomeField(); field != nil { ... } ``` The important part is that there's no possibility for panicing due to nil pointer, where-as, previously, if the caller forgot to check for `record.R != nil`, a panic would happen. The change is backward compatible and follows the pattern that protobuf generation uses, i.e. `Message.GetX() XType`.Configuration menu - View commit details
-
Copy full SHA for 915f16d - Browse repository at this point
Copy the full SHA 915f16dView commit details -
Configuration menu - View commit details
-
Copy full SHA for bc05a42 - Browse repository at this point
Copy the full SHA bc05a42View commit details -
Configuration menu - View commit details
-
Copy full SHA for c568b09 - Browse repository at this point
Copy the full SHA c568b09View commit details -
Configuration menu - View commit details
-
Copy full SHA for bc95b73 - Browse repository at this point
Copy the full SHA bc95b73View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.10.2...v4.11.0