diff options
| author | Federico Caselli <cfederico87@gmail.com> | 2023-01-18 23:02:36 +0100 |
|---|---|---|
| committer | Federico Caselli <cfederico87@gmail.com> | 2023-01-18 23:02:48 +0100 |
| commit | 8b4b26e709c906134d5277c3fa2220aa5c4bb428 (patch) | |
| tree | 14e94c3eb7da7017ff5416f1c8745c062aec8df4 | |
| parent | a5ffe24c907f8131dca513a8640ae888daa77510 (diff) | |
| download | sqlalchemy-8b4b26e709c906134d5277c3fa2220aa5c4bb428.tar.gz | |
avoid confusion in rst comment
Change-Id: I6e971f7445ae19f73097516b58776ab05a5371f1
| -rw-r--r-- | doc/build/tutorial/metadata.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/tutorial/metadata.rst b/doc/build/tutorial/metadata.rst index 5d1733fc6..730190be3 100644 --- a/doc/build/tutorial/metadata.rst +++ b/doc/build/tutorial/metadata.rst @@ -53,7 +53,7 @@ constructed programmatically, either directly by using the option to load some or all table information from an existing database, called :term:`reflection`. -.. note: the word "simply" is used below. While I dont like this word, I am +.. comment: the word "simply" is used below. While I dont like this word, I am using it here to stress that creating the MetaData directly will not introduce complexity (as long as one knows to associate it w/ declarative base) |