You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
📝 Update link to JetBrains Python survey in features.md (#1627)
Update link to JetBrains Python survey in features.md
Updated link to the 2024 JetBrains Python Developers Survey.
Co-authored-by: Sofie Van Landeghem <[email protected]>
Copy file name to clipboardExpand all lines: docs/features.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ Underneath, ✨ a **SQLModel** model is also a **SQLAlchemy** model. ✨
76
76
77
77
There was **a lot** of research and effort dedicated to make it that way. In particular, there was a lot of effort and experimentation in making a single model be **both a SQLAlchemy model and a Pydantic** model at the same time.
78
78
79
-
That means that you get all the power, robustness, and certainty of SQLAlchemy, the <ahref="https://www.jetbrains.com/lp/python-developers-survey-2020/"class="external-link"target="_blank">most widely used database library in Python</a>.
79
+
That means that you get all the power, robustness, and certainty of SQLAlchemy, the <ahref="https://lp.jetbrains.com/python-developers-survey-2024/#orms"class="external-link"target="_blank">most widely used database library in Python</a>.
80
80
81
81
**SQLModel** provides its own utilities to <abbrtitle="with type completion, type checks, etc.">improve the developer experience</abbr>, but underneath, it uses all of SQLAlchemy.
0 commit comments