docs: Fix a few typos

Browse Source 
There are small typos in:
- dataset/table.py
- docs/queries.rst
- docs/quickstart.rst

Fixes:
- Should read `significant` rather than `signficant`.
- Should read `parameterisation` rather than `paramterisation`.
- Should read `explicitly` rather than `explicetly`.

Signed-off-by: Tim Gates <tim.gates@iress.com>
This commit is contained in:
Tim Gates 2022-07-17 12:21:02 +10:00
parent be81e8f000
commit 976c25ad14
No known key found for this signature in database
GPG Key ID: AE3BE0D53823CF05
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
dataset/table.py
View File

@ -717,7 +717,7 @@ class Table(object):
def __iter__(self): def __iter__(self):
"""Return all rows of the table as simple dictionaries. """Return all rows of the table as simple dictionaries.
Allows for iterating over all rows in the table without explicetly Allows for iterating over all rows in the table without explicitly
calling :py:meth:`find() <dataset.Table.find>`. calling :py:meth:`find() <dataset.Table.find>`.
:: ::

2
docs/queries.rst
View File

@ -62,7 +62,7 @@ Queries using raw SQL
To run more complex queries with JOINs, or to perform GROUP BY-style To run more complex queries with JOINs, or to perform GROUP BY-style
aggregation, you can also use :py:meth:`db.query() <dataset.Database.query>` aggregation, you can also use :py:meth:`db.query() <dataset.Database.query>`
to run raw SQL queries instead. This also supports paramterisation to avoid to run raw SQL queries instead. This also supports parameterisation to avoid
SQL injections. SQL injections.
Finally, you should consider falling back to SQLAlchemy_ core to construct Finally, you should consider falling back to SQLAlchemy_ core to construct

2
docs/quickstart.rst
View File

@ -208,7 +208,7 @@ considered out of scope for the project, include:
* Support for Python 2.x * Support for Python 2.x
There's also some functionality that might be cool to support in the future, but There's also some functionality that might be cool to support in the future, but
that requires signficant engineering: that requires significant engineering:
* Async operations * Async operations
* Database-native ``UPSERT`` semantics * Database-native ``UPSERT`` semantics